projectM 2.1.0+dfsg-4build2 crashes with SIGABRT on first preset change

Bug #1855627 reported by Markus Birth
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fedora
Unknown
Unknown
projectm (Debian)
Fix Released
Unknown
projectm (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Starting projectM is fine and it comes up with the default visualisation, menu works, etc.. But as soon as you try to change to ANY other preset, it crashes with either

    free(): double free detected in tcache 2

or

    double free or corruption (fasttop)

It seems to be related to these ones:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924925

https://bugzilla.redhat.com/show_bug.cgi?id=1663047

https://bugzilla.redhat.com/show_bug.cgi?id=1631104

Also, 2.1.0 is a bit old now.

Changed in projectm (Debian):
status: Unknown → Confirmed
Revision history for this message
Boris Gjenero (boris-gjenero) wrote :

I'm also getting this crash in eoan. Building with a patch made from the commit linked in the Debian bug report ( https://github.com/projectM-visualizer/projectm/commit/c87f208c47252b47b117db73cc28a053d5133ffd ) makes it work.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in projectm (Ubuntu):
status: New → Confirmed
Changed in projectm (Debian):
status: Confirmed → Fix Released
Revision history for this message
Shane Synan (digitalcircuit) wrote :

projectM 2.1.0 was just removed from Debian due to being Qt 4 ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953118 ).. but upstream projectM release 3.1.3 is Qt 5 ( https://github.com/projectM-visualizer/projectm/releases ).

Time to file a new bug on the Debian bug tracker for reinclusion into the archives?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.