[Runtime Bug]: Gmotor Automobilista Memory leak

Describe the bug

When you launch Automobilista game and enable RTX remix, the amount of memory took by NVBRIDGE is growing with time.

How do you reproduce the bug?

Launch the game and enable RTX remix,
Gmotor2 Game : Automobilista 1

With 20 cars, on a track, starting with around 6.4GB/ ram after around 10 laps running : 15GB to 22GB used by
NvBridge.exe
Ending race, going back to menu, same amount of ram used (the ram still used until you close the game )
The AMS.exe process is still using around 500mb of ram (32bit executable with limit of 3.46gb) in game.

---

W&WO Culling enabled, restricting Culling.
rtx.conf and user.conf ligne added and bridge added
No results.

Tried :
----------RAMVRAM ISSUE---------------
rtx.uniqueObjectDistance = 0

rtx.terrainBaker.enableBaking = False

rtx.terrainBaker.clearTerrainBeforeBaking = False

rtx.useRayPortalVirtualInstanceMatching = False
rtx.recomputeTextureHashOnWrite = False

rtx.texturemanager.fixedBudgetEnable = True

rtx.texturemanager.fixedBudgetMiB = 1024

rtx.playerModel.enableVirtualInstances = False

-------- SETTING (on AMS) ----------------
Disable shadow (off)
Disable aniso(to be tested with and without)
--------BRIDGE.CONF ----------------------
bridge.sharedMemorySizeMB = 4096
bridge.clientMemoryBudgetMB = 2048
bridge.executableBlacklist = AMS Config.exe, GID.exe, Dedicated.exe
sendAllServerResponses = False
useSharedHeap = True
sharedHeapPolicy = Textures,StaticBuffers

What is the expected behavior?

No response

Version

1.5.2

Logs

bridge32.log
crash-upload.log
remix-dxvk.log

Crash dumps

No response

Media

No response

Start by reproducing the Automobilista 1 scenario with RTX Remix enabled, then inspect bridge32.log, crash-upload.log, and remix-dxvk.log while monitoring NvBridge.exe across several laps and after returning to the menu. Done means isolating the source of the reported memory growth and verifying that memory no longer continues to accumulate under the described settings.