Skip to content
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

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

Open
mixxxbot opened this issue Aug 22, 2022 · 7 comments
Open

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

mixxxbot opened this issue Aug 22, 2022 · 7 comments

Comments

@mixxxbot
Copy link
Collaborator

Reported by: daschuer
Date: 2012-06-26T08:31:38Z
Status: Confirmed
Importance: Wishlist
Launchpad Issue: lp1017858
Tags: polish


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.

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2012-06-26T21:27:59Z


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

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2014-03-18T19:45:37Z


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

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2014-04-15T15:32:34Z


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?
c9ebfad

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.

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2014-04-15T15:33:23Z


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

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2014-04-15T17:05:44Z


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.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2014-04-15T18:22:08Z


+1 for the pop up.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2014-10-11T20:53:33Z


Related Bug #⁠1380171

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant