Closed Bug 502958 Opened 15 years ago Closed 13 years ago

Automatically start in Safe Mode when Firefox dies at startup

Categories

(Toolkit :: Startup and Profile System, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 294260
Tracking Status
status2.0 --- wontfix

People

(Reporter: mkohler, Unassigned)

References

(Blocks 1 open bug)

Details

Firefox should automatically start in Safe Mode after it crashed for x times at startup. This would be useful for all toolkit apps. Specifying until which point it has to go is not that easy, I guess.

(please move this bug to the appropriate component, I've no idea where that should go to - toolkit?)
Flags: wanted-firefox3.6?
Component: General → Startup and Profile System
Flags: wanted-firefox3.6?
Product: Firefox → Toolkit
QA Contact: general → startup
Flags: wanted1.9.2?
Fixing bug 347680 will be a big step in this direction.
I suggest to make a meta-bug with this bug.
Depends on: 347680
No longer depends on: 347680
This should also apply to hangs and DEP deaths, not just crashes.
Summary: Automatically start in Safe Mode when Firefox crashes at startup → Automatically start in Safe Mode when Firefox dies at startup
Blocks: safe-mode
status2.0: --- → ?
Flags: wanted1.9.2?
(In reply to comment #1)
> Fixing bug 347680 will be a big step in this direction.

I don't think so, actually. If we crash at startup, we don't even reach session restore. We usually come into this problem because we're loading incompatible binaries of some sort, potentially from add-ons.
Starting into safe mode will enable us to run automated update and load add-on blocklists in that case, while starting even as far as into displaying the session restore tab already enables all add-ons and therefore will crash in those cases.
We need to hook in very soon in the startup process, in a place before safe mode makes a difference of what we are doing.
This appears to be a duplicate of bug 294260
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.