AnthorNet/SC-InteractiveMap

Excessive VRAM memory usage

Closed this issue · 7 comments

Issue

I have notified Interactive Map becomes slow after a short period of time and use lot of VRAM.

Replication

  1. Open a save with a big factory (no need of a mega factory)
  2. Zoom in and out on the map for one minute on crowded areas.

Actual Result

VRAM usage goes really high (8-10 GB) quickly.
The map freeze from time to time, especially after tab switching.

Task Manager
This is with very few tabs and programs running in the background.
I have 32 GB of RAM and a 1080 TI so available memory should not be issue.

Expected Result

VRAM usage stay reasonable, no freezes (eg: Google Maps stays below 1 GB).

Yeah but Google maps doesn't draw thousands of polygon, I'm doing a whole lot of optimisation every now and then, but not sure much can be done.

Have you tried lowering the polygon details under options?

I have tried low detail mode but it does not really help (I did a full refresh and make sure it's applied correctly (eg: buildings now looks like a dummy square). GPU usage still reach 10GB after several zoom in / out.
I understand it does lot of rendering calls but I don't think it should use that much memory.
Would there be a possibility there is some memory leak ? (eg: non disposed objects / buffers)

Can you reproduce it at your side ?

Just tested some Zoom In and Out, and the memory was moving back and forth as expected, did not notice any excessive usage?
Can I get your save to run more specific tests?

@AnthorNet : I'm unsure why you closed the topic because issue is still there:
image
With just a small amount of zoom in / out.

To ease 1.0 issues, and still cannot reproduce...

@tigrouind this is most likely a bug in your GPU driver

@tigrouind this is most likely a bug in your GPU driver

Thank you. I was using 537.34 (2023.9.12) and upgraded to 561.09 (2024.9.11). It fixed the issue.

Please note that I was already using latest driver when this ticket was created and even updated afterwards. It took NVidia a while to fix this.