Safe Mode: Provide fail safe start for Mixxx after it has crashed

Bug #1017858 reported by Daniel Schürmann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Confirmed
Wishlist
Unassigned

Bug Description

Its a bad thing when someone whants to try mixxx and it crashes after start, without any message.

Mixxx should detect that and start in a failsafe mode which is more likly able to start.
This could be achieved to by writing a temp file on mixxx start and delete it on Mixxx shutdown.
If Mixxx finds this file when starting, the last run crashed and it should ask the user if he wants to try the failsafe mode.

Example:
See: Bug #1008999 Segfault on WinXP in Virtual Box using GL Waveforms Edit.
In this case fail save mode is starting with an empty waveform.

Tags: polish
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

I would also like to add crash reporting to such a fail-safe system using something like google-breakpad.

Changed in mixxx:
status: New → Confirmed
importance: Undecided → Wishlist
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Related to Bug #1191904 (maybe that one is a dupe of this actually -- oops).

summary: - Provide fail save start for Mixxx
+ Safe Mode: Provide fail safe start for Mixxx after it has crashed
RJ Skerry-Ryan (rryan)
tags: added: polish
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

I added a --safeMofe command-line flag. It currently:

* Uses empty waveforms.
* Turns off synchronization polling if it was enabled.
* Doesn't auto-open MIDI devices.
* Disables WSpinny.

What else should we do?
https://github.com/mixxxdj/mixxx/commit/c9ebfad121f066c7b38a76417137735102571894

This bug should now just be a matter of:
1) Detecting crashes
2) Enabling safe-mode automatically early on in bootup if we detect we crashed before.

We should be careful because this could be annoying if someone only has a crash on exit -- auto-enabling safe mode will make Mixxx less functional for them. Maybe we can write a check-point when we are about to shut down so that we can tell if we crashed during shutdown versus normal operation.

Changed in mixxx:
milestone: none → 1.12.0
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

I would call this is a 1.12.0 blocker... we lose too many users to repeated crashes on bootup, etc.

Revision history for this message
Owen Williams (ywwg) wrote :

I was thinking, after we detect a crash on shutdown, to pop up a box the next time saying "hey, yo, mixxx crashed, do you want to send us a log?" Of course we'd have to do this before we overwrite the log! We could expand that box to include "do you want to start in safe mode" which would clear out audio config, switch to safe waveforms, and use a conservative skin.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

+1 for the pop up.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Related Bug #1380171

RJ Skerry-Ryan (rryan)
Changed in mixxx:
milestone: 2.0.0 → none
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/6544

lock status: Metadata changes locked and limited to project staff
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.