Closed tux3 closed 1 year ago
Thanks for the report!
Which Poco library version are you using to build the application? There was a bug in a few Poco releases (1.10 to 1.11.1, inclusive) which I reported upstream, causing issues with freeing the command line options too early during parsing and then crashing the application in the destructor, which is what I can see in your crash report as well. Due to the nature of the issue, there's also a possibility of use-after-free which can lead to further heap corruption, crashing the application randomly.
If you're using one of the affected Poco versions, please either downgrade to Poco 1.9.x or upgrade to 1.11.2 or later, all of them don't have the issue. Some Linux distros still have the broken versions, so you'd need to either link Poco statically or set RPATH accordingly so your application always uses your self-built .so files.
I have Poco 1.11.0-3+b1 from Debian sid.
So that's probably it, thank you! =)
Hello,
I was running the SDL frontend and got this SIGABRT
Looking at coredumpctl, it seems to crash frequently:
I build projectM and the sdl frontend from source today, so both are up-to-date.
Here's all the coredumps I have (in two zip files, because Github upload limits): crashes.zip crashes2.zip
And here's the coredump info and backtrace from one of them, if that helps:
I think this one might actually have crashed on exit (not while playing), but if it's a memory corruption that free() only detects on exit, I supposed it might have happened earlier (might be worth checking with Valgrind?).
Cheers