-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crash: Could not allocate 10240 bytes #4523
Comments
Given the allocation error message, it's worth noting that my system has ample free RAM. |
I don't see that error message in the logs. We generally also don't really support Linux/Wine explicitly, as we've seen obscure bugs there over the years that are just extremely hard to track down. Where did you get that error message? I'd need at least a stack trace or something. |
I think it's still worth noting, since bugs that surface on Linux/Wine are often also present (but harder to notice) on Windows. I'm hoping the message might help identify a crash that affects all users but hasn't been tracked down yet.
As I said, the message was printed to the console, so either stderr or stdout. (I launched HDT from a command prompt so I could see any such messages.)
Do you have a debug build that will generate a stack trace on abnormal exit? |
For what it's worth, a search for that error message turns up this report of code that allocates many strings, as might occur if there was an object leak. |
Expected Behavior
No crashes
Actual Behavior
HDT sometimes crashes midway through a match.
I don't see an obvious sign of the crash in the log, but I watched the console output last time it happened, and saw this message:
Steps to reproduce behavior
I have not found a way to reproduce the crash on demand.
From memory, I think I have only seen it happen while I was playing a match; not while navigating menus. (I am not absolutely certain of this, though.)
I'm running in Linux/Wine/Mono, so it's possible that the console output I quoted above will be different (or even absent) for people running in Windows/DotNET.
Log/Screenshots
hdt_log_redacted.txt
The text was updated successfully, but these errors were encountered: