-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
midi.sendShortMsg result in segmentation fault - armhf - 2.2.4 - 2.3.1 - 2.40-alpha #10632
Comments
Commented by: mhe1234 |
Commented by: ronso0 Mixxx 2.2 doesn't receive bug fixes or support anymore. Can you build 2.3 (or main branch 2.4) for the Pi? |
Commented by: mhe1234 Yes, 2.3.1 -> 2.3.1-30-gecab893971 platform Linux ARM Options -> preferences main release building right now |
Commented by: mhe1234 2.4.0-alpha-pre platform Linux ARM Options -> preferences All versions gave segmentation faults. |
Commented by: mhe1234
|
Commented by: ronso0 I can't comment on the actual root issue here (how user data can crash Mixxx) but it seems the script trying to stop nonexistant timers may be the trigger. Please try to reproduce the crash with the overhauled script MIDI-Output for lightcontrol script version from the forums |
Commented by: mhe1234 Tested on my 2.3.1-30-gecab893971 build. Forgot to save the previous deb (2.4 alpha). The updated script changed the behavior. Instead of crashing when hitting apply. It now crash when starting the song. |
Commented by: mhe1234 Did some extra digging, if i comment all midi.sendShortMsg out, script is not crashing.
it result in
The No protocol specified is displayed, just before segmentation fault. I dont think problem is in the Midi for light script. // edit
Just to be sure if the format is correct, it crashes. |
Commented by: mhe1234 Allright, fiddling more around. Instead of Selecting MIDI for light with Midi Through Port-0 result in segmentation fault Edit The title should be changed to: midi.sendShortMsg result in segmentation fault. |
Commented by: JoergAtGithub You could try to comment out the line Controller::triggerActivity() in /code/src/controllers/controller.cpp:112 |
Commented by: mhe1234 Hi, Recompiled the 2.3.1 version. Same result as described before. Thank you |
Commented by: Pegasus-RPG That piece of information and your last back trace suggests this may be an issue with your video driver or within XWindows. Can you see if there are any updates for both on your system and re-test? Can you get a new back trace with Controller::triggerActivity() commented out? Thank you for your help! |
Commented by: mhe1234 I am starting mixxx without xwindows: mixxx -platform vnc:size=1920x1280 --developer --controllerDebug --logLevel debug Will make new back trace. |
Commented by: mhe1234 I think inside midicontroller.cpp the two triggerActivity() should also be commented out.. // compiling now. |
Commented by: mhe1234 Can confirm, that with removing the other two triggerActivity, it isnt segfaulting anymore. |
Issue closed with status Fix Released. |
Reported by: mhe1234
Date: 2022-01-01T14:46:36Z
Status: Fix Released
Importance: Undecided
Launchpad Issue: lp1956144
Attachments: [mixxx debug.zip](https://bugs.launchpad.net/bugs/1956144/+attachment/5550539/+files/mixxx debug.zip), [mixxx debug 2.3.1.zip](https://bugs.launchpad.net/bugs/1956144/+attachment/5550637/+files/mixxx debug 2.3.1.zip), [mixxx debug 2.4.0-alpha.zip](https://bugs.launchpad.net/bugs/1956144/+attachment/5550678/+files/mixxx debug 2.4.0-alpha.zip), [gdb dump.txt](https://bugs.launchpad.net/bugs/1956144/+attachment/5552718/+files/gdb dump.txt)
Version 2.2.4
Raspberry pi
When starting mixxx:
mixxx -platform vnc:size=1920x1280 --developer
To reproduce:
Options -> Preferences
Controllers -> Midi Through Port-0
Tick box Enabled
Load preset: Midi for light
Click apply.
Result in direct segmentation fault.
If you restart mixxx, the controller is enabled, you see debug information and resulting again in a segmentation fault.
Attachment has gdb and terminal output information
Thank you !
The text was updated successfully, but these errors were encountered: