Resolved [UI] VRAM leaks in menu

Issue has been resolved with a patch or user intervention
Status
Not open for further replies.
E

Edziu

New member
Windows Version: Windows 10 Pro 22H2
PC Spec (CPU, GPU, RAM): 5800X3D, RX 7900 GRE 16GB, 32GB RAM
When did it happen? / What were you doing when it happened?: Menu slowly fills up my VRAM up to 16GB, happened once then I went to set up offline race the same way and happened again. I run the game on 6480x1216 resolution and basically struggling with VRAM use since I switched my gpu (I did that because of lack of VRAM on my previous card). I need to go Medium or lower settings on 16GB GPU just because of VRAM issues. My game froze many times today, and I suppose that's because of VRAM filling up to max
Attach trace & dump file (if applicable):
First trace is just menu filling up the VRAM, second one (bigger) is when I filled up the VRAM in menu then entered 7 min offline race after which the game froze as it usually does for me - mouse is visible, but I can't press anything and can't go back into main menu.
Sometimes when I experience such freeze at the end of the race is when I can move the camera freely like I was in replay mode but no buttons appear and other than Alt+F4 I cannot do anything

edit: video of vram filling up in menu (almost full)
 

Attachments

  • trace_2024_09_15_22_17_48-75.txt
    90.2 KB · Views: 5
  • trace_2024_09_15_22_40_54-65.txt
    609.3 KB · Views: 5
Last edited:
I checked this as well, after filling up the VRAM (16GB) the RAM gets filled up. This happens only in the Menus. Once you start driving the VRAM usage drops a few MB and the RAM usage decreases.

Checked with MSI Afterburner.

Testsystem:
- Win11 (Version 10.0.22631 Build 22631)
- CPU: Ryzen 7600
- Graphicscard: 7800XT
- RAM: 32GB
- latest update of LMU including DLC 1 and 2
 

Info Required - RAM Leak, i think it addresses a lot of bugs here mentioned

(Sys: 5900x on x570-chipset, dual channel 32GB (2*16) ram@3200MT/s , following amd specs (not 3600 or sth); 6800xt, playing @5120x1440 freesync, all stock: NO oc/uv/curve-optimization or other potential bullshit, memtest86-stable, clean w11 (23h2, 24h2 since yesterday) with up-to-date drivers*...
community.lemansultimate.com community.lemansultimate.com

In this thread we highlighted the same problem. I point out that we all use AMD GPUs. It makes me think that there is a connection.
 
Pete posted temporal solution last evening. It works for me. "for anyone having significant trouble with the 60s stutter issue i've set a new build live on the pub-share beta which should address the issue. Please be aware this is an experimental build with various updates to how we render the user interface, trying to help users with startup issues so your mileage may vary but this is the best we can do for this weekend. the memory leak we've been looking at is an AMD GPU specific issue that's only present for some users. It seems to be linked to CEF. This build does come with a newer version of CEF that has helped for some users but not all. You may also see improvements by disabling CEF GPU rendering by changing the following settings in: player/settings.json:
"CEF Async":true,
"CEF GPU Compositing":false,
"CEF GPU Rendering":false,
although be aware this will make your ui perform more slowly in most cases (You could also try other combinations but this is the most likely one to help)

(Note you'll need to run the pub-share build to generate these settings in your settings.json and the settings will only work on that build for now)"

TLDR: for AMD VRAM leak first of all install beta (game properties -> beta -> pub-share and delete settings.json so it gets replaced - verify to make sure it does. Otherwise you will not see those CEF settings, but maybe copying this formula into the file will be enough, I'm not sure.
 
Last edited:
Thanks, the workaround works. But oh boy, the menu now :ROFLMAO: Driving is supersmooth, that is the most important :)
Does anyone know what this CEF is doing? Anyway, VRAM is around 11,5GB now during driving and menu is somewhere around 3GB.

Thanks for the hint @Edziu. Have a nice weekend
 
If I do this and change the settings as shown, the ui is laggy, but when i go to join a practice session it just sits there and never loads the session.
 
Yes it's slow. I loaded into special event in 5 mins. At first I also thought it hanged but no. Maybe wait a little more. You can also check this thread specifically created for issues like you have. Maybe you'll find any solution there

Info Required - [UI] Issues MEGATHREAD

Trying to group some errors together to make them easier to log for the devs. Trace file instructions: https://community.lemansultimate.com/index.php?threads/read-me-first-how-to-log-a-bug-report.3/ This is for unexpected UI issues which could include, errors in functionality, display etc...
community.lemansultimate.com community.lemansultimate.com
 
Gulivert said:
Cef is chromium embedded framework.
Basically is to inject chromium inside an app and you can develop UI with web technologies. Which means the UI of LMU is web based, is like a website…

github.com

GitHub - chromiumembedded/cef: Chromium Embedded Framework (CEF). A simple framework for embedding Chromium-based browsers in other applications.

Chromium Embedded Framework (CEF). A simple framework for embedding Chromium-based browsers in other applications. - chromiumembedded/cef
github.com github.com
Click to expand...
Why does every problem somehow trace back to "JavaScript" 😂
 
Edziu said:
Pete posted temporal solution last evening. It works for me. "for anyone having significant trouble with the 60s stutter issue i've set a new build live on the pub-share beta which should address the issue. Please be aware this is an experimental build with various updates to how we render the user interface, trying to help users with startup issues so your mileage may vary but this is the best we can do for this weekend. the memory leak we've been looking at is an AMD GPU specific issue that's only present for some users. It seems to be linked to CEF. This build does come with a newer version of CEF that has helped for some users but not all. You may also see improvements by disabling CEF GPU rendering by changing the following settings in: player/settings.json:
"CEF Async":true,
"CEF GPU Compositing":false,
"CEF GPU Rendering":false,
although be aware this will make your ui perform more slowly in most cases (You could also try other combinations but this is the most likely one to help)

(Note you'll need to run the pub-share build to generate these settings in your settings.json and the settings will only work on that build for now)"

TLDR: for AMD VRAM leak first of all install beta (game properties -> beta -> pub-share and delete settings.json so it gets replaced - verify to make sure it does. Otherwise you will not see those CEF settings, but maybe copying this formula into the file will be enough, I'm not sure.
Click to expand...
This was a good resolution for me. With the suggested "CEF" settings the menus run smoothly, loading the game session (online) didn't seem to slow down much, and in game my RAM is occupied for a value just under 9000 MB (9GB). In these days I will try to run online to see if everything wants to go the right way.
 
I reverted the CEF settings, I couldn't choose a car anymore. Was always picking the "initial" car of the class. Anyway, I did not had any crashes before and the VRAM leak is at least slower than before. A plus of this branch is, no stuttering anymore, which could be related to the VRAM to be honest and the artifacts with AMD cards seem to be fixed as well :)
 
Did a bit of a stress test. I changed to the pub-share beta and then loaded the sim. I THEN had to leave to take my wife to an appointment so I left the game running at one of the menus. Got back about an hour later and the menus all responded, no lockup. There was a noticeable hitch in the menu animation about 3/4ths of the way through the curtain pullback. Had to reset my Driver name, and then first load of the COTA track felt slower, there was a noticeable pause at 48%...since I haven't had to worry about that in the past, that caught my eye. But then it kept loading, although slower.
On track, the artifacts around the windscreen wiper were non-existent. So this solution appears well on the way of curing both AMD videocard issues. (Memory leak and onscreen blocks) Hopefully they will be able to keep the cure and get the menu smoothness back. However, given the choice, I'd gladly suffer a slight hitch in an animation wipe than have graphic issues on track.
I should have paid attention to the car choice. I changed from an Aston Martin GTE to the Alpine, and then to the WEC Alpine, but I didn't try and select another car in either category.
 
The only thing I can offer.

Does anyone here use AVG Tuneup.
I like it because it handles a lot of cleanup.
If I do a fresh Lemans I find Tuneup reports a issue.

LMU is in startup ?
It is not in Windows Startup ( you won't see it ) but it's in AVG Startup ....okay.

Why is it there at all ? I have every sim, none do this in AVG Tuneup ?
Yeah I know it says "no impact" which is also odd as I dont' think I have never had anything report this, always low impact at least.

Screenshot 2024-09-09 141157.jpg
Screenshot 2024-09-09 141221.jpg
 
Last edited:
Edziu said:
Pete posted temporal solution last evening. It works for me. "for anyone having significant trouble with the 60s stutter issue i've set a new build live on the pub-share beta which should address the issue. Please be aware this is an experimental build with various updates to how we render the user interface, trying to help users with startup issues so your mileage may vary but this is the best we can do for this weekend. the memory leak we've been looking at is an AMD GPU specific issue that's only present for some users. It seems to be linked to CEF. This build does come with a newer version of CEF that has helped for some users but not all. You may also see improvements by disabling CEF GPU rendering by changing the following settings in: player/settings.json:
"CEF Async":true,
"CEF GPU Compositing":false,
"CEF GPU Rendering":false,
although be aware this will make your ui perform more slowly in most cases (You could also try other combinations but this is the most likely one to help)

(Note you'll need to run the pub-share build to generate these settings in your settings.json and the settings will only work on that build for now)"

TLDR: for AMD VRAM leak first of all install beta (game properties -> beta -> pub-share and delete settings.json so it gets replaced - verify to make sure it does. Otherwise you will not see those CEF settings, but maybe copying this formula into the file will be enough, I'm not sure.
Click to expand...
I have been looking for a solution to the menu problem for 10 days. I have a Rx 6800 16 gb graphics card. I applied your suggestion and the problem was solved, thank you.
 
one thing I found was to change the menu to a different screen. There are 4 options, I think choosing the first one could solve the problem if you are on the setup page. Possibly even if you are already using the first screen tab, making the change to any other tab before pressing DRIVE may clear the screen.
 
Status
Not open for further replies.
Back
Top