Search the Community
Showing results for tags 'Memory Leak'.
Bug: After running for multiple hours game appears to run more sluggishly, enough so it becomes noticeable to the naked eye. Repro Steps: 1. Start Game 2. Play it for hours on end because it's awesome. 3. Observe degraded performance. Notes: 1. I have not confirmed if this is tied into the loading of new assets. From observation it appears that new assets get loaded into temporary memory as you play the game and then are dumped when you exit game. As such multiple summons, monsters, and areas slowly bloating the memory footprint may be relevant. Or it may not be. Coding is hard :D. 2. The area I found this most easy to notice is right in front of the Wild Mare in Queen's Berth. The copious amount of water there seems to put a small strain on my system I can barely notice during fresh starts. After playing for awhile this degrades considerably though to where it FEELS like it was under 30 FPS, perhaps as low as 20. 3. I've only been able to repro this 3 times so far, but it's been consistent. No idea of hours needed to repro as I'm busy being sucked into the game lol. My guess would be 3+ but I'd also try 5+. As mentioned making it load as many assets as possible in temporary memory may impact this if that ends up being relevant. DxDiag.txt
I've got a memory leak in the game when trying to load form a saved game as well as a few crashes prior. If you could check it out it would be appreciated. I have the error and dump file as well, just need to know where i can send such a thing. output_log.txt
This seems to get progressively worse until it takes about a minute to disarm traps. The game stutters more and more when disarming traps until eventually it freezes for 10-20 seconds. This only happens when disarming traps, and the only issue I'm experiencing. The rest of my computer seems to continue normally (ie: a video, or audio continues playing while this stalling happens).
NOTE: The forum prevents me from uploading a .7z file, so I have changed the extension to .bmp. If you want to look at the crash dump, change the extension back to .7z. [Description of the issue] Loading of saved games, both normal and quick, results in a memory leak that will eventually cause a crash. [steps to Reproduce] Start a new game, default character, default settings. Resolution for me is 2560x1440. Save/quicksave the game as soon as it is loaded. Note the memory usage in Task Manager (or Process Explorer). Repeatedly load/quickload the game, noting how the memory footprint increases by 80 to 120 MB per load (more or less). The first load is usually a large jump in memory footprint. After around 15 loads (around 3400 MB total memory footprint) the game will no longer quicksave. The quicksave button will cause the shadows to shift, but nothing else. On the 16th load, the game fails to load and generates a crash dump (see attached file). [Expected Behaviour] Loading should use a constant amount of memory. [Other Remarks / Comments] Saving seems to have no affect on the memory footprint. Quitting to the main menu and loading a game from there does not reduce the memory footprint. 2014-08-19_174932.bmp