Closed Bug 926362 Opened 11 years ago Closed 11 years ago

Add support for disabling safe mode at launch.

Categories

(Firefox :: Session Restore, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: jujjyl, Unassigned)

Details

I am trying to automate Firefox to run unit tests from buildbot. What I do is I typically run C:/Program Files (x86)/Aurora/firefox.exe --no-remote -P aurora -private http://localhost:5103/Tests_d.html to run the tests. This works, up until something in the Tests_d.html behaves badly, in which case buildbot will kill the process. When this happens, the next time Buildbot tries to launch a Firefox process for viewing a web page, one of the following dialogs will pop up: https://dl.dropboxusercontent.com/u/40949268/firefox_safemode.png I would like to disable the safe mode startup detection feature altogether, and always launch Firefox in standard mode, but there does not seem to be an option to do so. Could Firefox add a --no-safe-mode command line startup option that would disable the did-previous-run-crash safe mode check for the current run, or a pref in about:config that would disable the safe-mode popups and always force startup in default mode? Either would be fine for this use case.
OS: Windows 7 → All
Hardware: x86_64 → All
This is not Firefox related and most likely also not buildbot. I think you need a better wrapper script for Firefox, and most likely you also want to create a fresh profile for each run. We have no component in our Bugzilla instance which is about buildbot integration. So you might better file a bug on its own bug tracker or we can figure it out in our #automation channel on IRC.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
I dug through the sources and realize now that setting browser.sessionstore.max_resumed_crashes = -1 and toolkit.startup.max_resumed_crashes = -1 will do exactly what I want. I had set those both to zero, assuming that would disable them. But looks like -1 is the value to disable instead! Thanks to anyone who spent time reading this :)
You need to log in before you can comment on or make changes to this bug.