Memory leak seems to have resurfaced

[Sharrnah]

I played in VR when i noticed that Desktop+ eats 11 GB of VRAM (pretty much all of the remaining VRAM i had at that moment)

So i restarted Desktop+ from the ingame menu which solved it for the moment.

After some time my whole PC crashed. Unsure if that crash was from the memory leak or from something else though.

See #64 when i reported a similar issue. Maybe its possible that recent changes introduced this issue again.

Also Possible that it is related to the Desktop+ Browser since i use 2 overlays mostly with another hidden browser overlay depending on need.

I have a NVIDIA RTX 3090 Driver v566.36
Windows 11 x64
Latest Desktop+ Version 3.1

I will try some more things and see if i can find a setting which fixes this

[elvissteinjr]

That VRAM leak still remains a mystery to me to be honest. As was noted, I only really mitigated the issue by cutting down the amount of individual texture sharing calls significantly.

With that being said, I'd say the first point of interest here would be comparing the last two Desktop+ Browser versions.
I have not dug into the internal changes to the CEF codebase (the OBS guys seem to have put quite a bit of work in with each version though), but I have observed a complete lack of shared texture re-use compared to previous versions... which might be the culprit. We'd be looking at shared texture allocation for each frame again then.

Just... in that case I don't really think I can easily swoop in and work around it. Not to mention I still can't reproduce this, even on a newer GPU now.
Also appears to remain a somewhat isolated case. At least I haven't heard of anyone else yet.

[Sharrnah]

Thanks. Maybe its specific to my usecase. I expect most people to use a browser overlay, suft some and then close it. At most maybe having a single browser open at a time.

I use it for a type of subtitle. with transparency (Which Desktop+ is the only one so far i have found to support browser transparency in overlays)

Since it is live subtitles it updates very often.

But it could also be a driver bug. The later NVIDIA drivers aren't particular known for being bug-free.

I am aware its hard to debug if its such a edge-case apparently.

I will see if i can pinpoint it somehow.