Descriptive Problem Summary:
After 4 hours "Dream Daemon has stopped working error" occurs
Problem signature:
Problem Event Name: APPCRASH
Application Name: dreamdaemon.exe
Application Version: 5.0.514.1583
Application Timestamp: 623ccae0
Fault Module Name: MSVCR120.dll
Fault Module Version: 12.0.21005.1
Fault Module Timestamp: 524f7ce6
Exception Code: c0000005
Exception Offset: 000345ac
OS Version: 6.2.9200.2.0.0.272.7
Locale ID: 1033
Additional Information 1: 95dc
Additional Information 2: 95dc9e2d3e7603883adbb1f6c6919188
Additional Information 3: 46e7
Additional Information 4: 46e7012fa593441edc4c45ad4bc217d6
Numbered Steps to Reproduce Problem:
Code Snippet (if applicable) to Reproduce Problem:
Expected Results:
No crash, game runs smoothly
Actual Results:
Crash after 3-4 hours, memory appears fine at 100-200mb, no lag or slowdown or any indication prior
Does the problem occur:
Every time? Or how often? Everytime, 3-4 hours
In other games? N/A
In other user accounts? N/A
On other computers? N/A
When does the problem NOT occur? It did not occur last wipe with same files.
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
We upgraded Byond after the first crash. Still occurs.
We have reinstalled C++ runtimes.
Workarounds: Unknown
ID:2784890
 Apr 23 2022, 4:56 pm
|
|||||||||||||
| |||||||||||||
No minidump file can be found, not in %System Root%/Minidump, or anywhere on C:\ with a *. search.
Memory stays perfectly at 125mb, it doesn't seem to scale higher than this. We will revert to version 514 and see if the crash still occurs. Note that this crash only occurs with 100+ players and prior to this was hosted for a week on the same Byond version without issue. | |
It appears to be a memory leak
 | |
I would suggest taking periodic looks at the memory usage of the process using DD's own memory report tool. That can tell you what (general) kinds of objects are in use and how much memory they're using, which can help point to any issues that might be happening in your code.
Not ruling out an engine bug, but if such an issue exists it'd need a test case to narrow down the cause. | |
You can also generally confirm a byond memory leak by seeing if it persists byond a world/reboot.
look at the starting memory usage when you start up a server world reboot it immediately. Look at the post-reboot usage. Wait for memory to get insanely high. world reboot it again. If it's significantly higher then the first post-reboot usage then there is likely a byond side memory leak. | |
It is however possible you hit some kind of out-of-memory situation. How does the game perform on memory over time?