i’ve been keeping tabs on how the game exe does its thing over the last few days;
doesn’t matter if i’m idle or playing, it’s going to crash, and usually in the same way.
vram usage doesn’t seem to climb, but actual ram does, sort of. it doesn’t use up all of my 64gb of ram, but it does general kill itself after hitting an overall size.
on absolute start (first black screen, and then the first video, it’s using 1.14GB.
2.74GB at press any key screen.
~2.3GB at char select.
~3GB at idle first entering a game.
but no, the interesting part is that with d2r closed my browser windows with tabs of game info and whatever doesn’t tend to expand memory much. with d2r open, the ram usage they utilize steadily climbs.
i can observe this with multiple browsers. including just opening a single ~30kb text file in a single window in one browser.
while they are steady in memory usage prior to the game launching, ram usage spikes and then climbs. closing the game doesn’t seem to stop this new behavior.
palemoon can be restarted and open the same pages i’ve always opened and i can wait until resource usage stabilizes. i can wait, it might flux a few dozen kb, but its not going to spike hundreds of mb and then keep rising.
the second i click the play button in the bnet client, memory usage starts it new oddness. i went from 2.14GB of ram with palemoon steady and idle to now 2.24GB and its climbing even now. all i did was launch and go into a game, then close d2r.
all active chrome and vivaldi pids are seeing a similar pattern of memory usage. stable after relaunch and waiting for idle, memory usage fluxing the usual small amount, but nothing special. launch d2r… everything starts rising.
i’m now at 2.26GB for palemoon just during the time i’ve written this part. and still climbing. 2.27.
reallllllly starting to wonder what the heck.