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
Mixxx doesn't exit cleanly (cmetrics?) #4969
Comments
Commented by: asantoni
|
Commented by: asantoni Full backtrace from above, and important note at bottom: (gdb) thread apply all bt
Mixxx's output: (hangs here... see note below) ====== Important Note: |
Commented by: muzzik101 Not sure if this will help, but this was a problem I noticed with the 1.6 beta 2 and it's still there in th 1.6 beta 3: On Windows XP SP2, whenever I close/exit Mixxx, if I open the task manager and look at open applications, Mixxx is not listed. But If I view running processes, Mixxx.exe is still running. When I try to end the process, it will not end. If I re-open Mixxx and close/exit another Mixxx.exe process is left running. I have seen as many as 5 Mixxx.exe processes running at once after opening and closing the program multiple times. The only way for me to end all of the processes is to re-boot. |
Commented by: muzzik101 I did some testing and found that the Mixxx.exe process only stays open on exit if a MIDI device is connected. Here is a screenshot of my running processes. |
Commented by: asantoni Jayson: I've built a new win32 package using today's SVN, and it's compiled without CMetrics support. I suspect this may be causing your hangs. Please test this and let us know if this problem still occurs. Your testing has been very useful in tracking down this bug thus far. :) Thanks! |
Commented by: muzzik101 Hi Albert, thanks for your help. I installed the new win32 Mixxx package and I have been doing some testing. When I run Mixxx with a MIDI controller connected, then exit Mixx, a Mixxx.exe process is is still left running (same as with the 1.6 beta 3). Now, with the new package, if I restart Mixxx while a Mixxx.exe process is still running, Mixxx crashes. Maybe this could be a problem related to my MIDI controller? I'm using the M-AUDIO Trigger Finger. Everything else about Mixxx has been great and other than this problem, Mixxx has been working really well for me. Let me know if there is anything else I can do to help. |
Commented by: asantoni Jayson: I'm still stumped here, but I'd like to put more time into this bug. What happens if you unplug your MIDI controller before running Mixxx and then close Mixxx? Make sure you wait at least 30 seconds before checking the process list to see if Mixxx.exe is gone. Also, can you check to see if this bug still occurs with Beta 4? Thanks, |
Commented by: Pegasus-RPG Please test in Mixxx 1.6.1. If we don't hear back from you in 7 days, we will close this bug. |
Issue closed with status Fix Released. |
Reported by: mathiasftl
Date: 2008-05-28T13:14:13Z
Status: Fix Released
Importance: High
Launchpad Issue: lp235479
Tags: backtrace, beta, cmetrics, fatal, old, windows
Attachments: Mixxx1.6_exit_process_bug.GIF
On WinXP 32bit with MIXXX 1.6 betas
setting the input controller device appropriate works fine. reopening MIXXX results in the device setting being resetted to the first one if there is more than one device. you have to set the control device everytime you start up.
The text was updated successfully, but these errors were encountered: