Crash/segfault when enabling/disabling chatty MIDI controllers
Bug #1073484 reported by
Sean M. Pappalardo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Fix Released
|
Critical
|
Sean M. Pappalardo | ||
1.11 |
Fix Released
|
Critical
|
Sean M. Pappalardo | ||
portmidi (Debian) |
Fix Released
|
Unknown
|
|||
portmidi (Ubuntu) |
Fix Released
|
High
|
Alessio Treglia | ||
Lucid |
Fix Released
|
High
|
Unassigned | ||
Oneiric |
Fix Released
|
High
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Unassigned | ||
Quantal |
Fix Released
|
High
|
Unassigned |
Bug Description
When disabling a very chatty controller (moving platter) and enabling another (non-chatty, doesn't matter which) I get a segfault. This happens with no tracks loaded. (The SCS.1d is the controller in question in this case and it constantly sends timestamp messages even when it's stopped. FWIW, these are Sysex messages that are 18 bytes long.)
Steps to reproduce:
1) Connect and turn on a very chatty controller
2) Start Mixxx.
3) Go to prefs and enable said controller, disabling all others. Click OK.
4) Go back to prefs, un-check Enable on the chatty controller, check Enable on another (like Midi-Through) and click OK.
5) Observe the segfault in Pm_Poll().
Happens in 1.11 r3447 & 3450.
summary: |
- Crash/segfault after analyze with MIDI controllers operating + Crash/segfault when enabling/disabling chatty MIDI controllers |
Changed in portmidi (Debian): | |
status: | Unknown → Confirmed |
Changed in portmidi (Debian): | |
status: | Confirmed → Fix Released |
Changed in portmidi (Ubuntu): | |
importance: | Undecided → High |
assignee: | nobody → Alessio Treglia (quadrispro) |
status: | New → In Progress |
Changed in portmidi (Ubuntu): | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Attached another back trace where the crash happened right after disabling one controller while enabling another.