crash: Could not allocate 10240 bytes

[foresto]

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:

Could not allocate 10240 bytes

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

[foresto]

Given the allocation error message, it's worth noting that my system has ample free RAM.

[beheh]

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.

[foresto]

We generally also don't really support Linux/Wine explicitly,

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.

Where did you get that error message?

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.)

I'd need at least a stack trace or something.

Do you have a debug build that will generate a stack trace on abnormal exit?

[foresto]

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.