Closed
Bug 85437
Opened 23 years ago
Closed 23 years ago
restart mozilla -turbo immediately after a crash
Categories
(Core Graveyard :: Cmd-line Features, enhancement)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9.4
People
(Reporter: dont, Assigned: dead)
References
Details
Crashes take forever to recover from on Windows, so why not add an extra couple of seconds to reset the -turbo mode if Mozilla was originally started with it? Thx.
Comment 1•23 years ago
|
||
Crashes take a long time on Win2K because of Doctor Watson. However, I think what this bug is requesting is that if Mozilla IPC server crashes then the next time mozilla is run restart the IPC server and display the browser. This would require the turbo option to be a preference (which it will be soon I am sure) and some additional logic in the moz startup to check this pref and make sure the IPC server is still running.
good idea. this is actually possible, although i'm not sure everyone will go for it. We probably should do like talkback and count crashes/interval. if we crash >2 times in <a few minutes we should throw an alert suggesting that the user upgrade and admitting that respawning -turbo is probably a bad idea.
Assignee: asa → law
Status: UNCONFIRMED → NEW
Component: Browser-General → XP Apps: Cmd-line Features
Ever confirmed: true
QA Contact: doronr → sairuh
Updated•23 years ago
|
QA Contact: sairuh → paw
Comment 3•23 years ago
|
||
See also bug 89511, restart -turbo when restarting mozilla after a crash.
Blocks: 75599
Summary: restart mozilla -turbo after crash → restart mozilla -turbo immediately after a crash
Comment 5•23 years ago
|
||
My bug (re-enter -turbo mode when restarting Mozilla after a crash) was marked as a duplicate of this bug, but I disagree with the approach this bug is taking. Restarting it immediately after a crash is dangerous, because it may lead to an infinite crash loop (something that happens to me occasionally with IE, by the way), and because the user is likely to be trying to relaunch the browser manually at the same time.
Comment 7•23 years ago
|
||
Fixed by the patch in bug 89504.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.4
Comment 8•23 years ago
|
||
nav triage: marking as dupe. QA - please verify both bugs when 89504 is fixed. *** This bug has been marked as a duplicate of 89504 ***
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Comment 9•23 years ago
|
||
Please leave these open, they need to be verified separately anyways.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 10•23 years ago
|
||
Fixed.
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
Updated•23 years ago
|
QA Contact: paw → tpreston
Comment 12•23 years ago
|
||
This has regressed: bug 103786.
You need to log in
before you can comment on or make changes to this bug.
Description
•