Closed
Bug 1048700
Opened 11 years ago
Closed 11 years ago
"Restart" in Breakpad doesn't restart the app
Categories
(Toolkit :: Crash Reporting, defect)
Tracking
()
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| firefox31 | --- | unaffected |
| firefox34 | --- | unaffected |
| firefox-esr24 | --- | affected |
People
(Reporter: tonymec, Unassigned)
Details
(Whiteboard: seamonkey-2.27-affected)
The "Restart" and "Quit" buttons (or radio buttons?) in Breakpad have the same effect: neither of them restarts the app.
I've noticed this in the following version of SeaMonkey; there's no newer Linux version at ftp.mozilla.org
Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 SeaMonkey/2.27a1 ID:20140214003001 c-c:1ce77c2f9bd0 m-c:d275eebfae04
I have also noticed it a few days ago in Firefox 24 ESR. I haven't tried the Nightly (Trunk) version of Firefox.
I suppose that killing the app with SIGSEGV or SIGILL would raise Breakpad, but I'm not sure I'd be well-advised to send such a bogus crash report to Mozilla just to see if Breakpad restarts that version of the app; or even worse, to send as many of them as necessary to bisect the error if I can find a "good" build earlier or later than the ones I tested.
| Reporter | ||
Updated•11 years ago
|
status-firefox-esr24:
--- → affected
Whiteboard: seamonkey-2.27-affected
Comment 1•11 years ago
|
||
I just tested with Firefox 31 (the default browser on Ubuntu 14.04) and "Restart Firefox" works here. I also tested with a nightly build and it worked fine there as well.
You can kill -ABRT <pid> to test, FWIW.
| Reporter | ||
Comment 2•11 years ago
|
||
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #1)
> I just tested with Firefox 31 (the default browser on Ubuntu 14.04) and
> "Restart Firefox" works here. I also tested with a nightly build and it
> worked fine there as well.
>
> You can kill -ABRT <pid> to test, FWIW.
I'll test it further here, not immediately but probably today, and report here.
| Reporter | ||
Comment 3•11 years ago
|
||
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20140805 Firefox/24.0 ID:20140805000540 CSet:bce71a749a08
(with my usual Fx24ESR profile) is BAD, even in Safe Mode and even without "Send crash data to Mozilla" (kill -6 i.e. SIGABRT).
| Reporter | ||
Comment 4•11 years ago
|
||
Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0 ID:20140805030300 CSet: 7f81be7db528
in a "testing" profile (not really virgin but almost), with kill -6 and without "Send to Mozilla" is GOOD, even in non-Safe mode.
I suppose I'll just have to wait until SeaMonkey Linux builds resume...
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Updated•11 years ago
|
status-firefox34:
--- → unaffected
| Reporter | ||
Comment 5•11 years ago
|
||
I suppose the fix must have landed between Mozilla 30a1 (Sm 27.7a1) of 2012-02-14, and Mozilla 31 (Fx31) release; but I cannot pinpoint the bug. If you find it this can be marked DUPLICATE.
| Reporter | ||
Updated•11 years ago
|
status-firefox31:
--- → unaffected
| Reporter | ||
Comment 6•11 years ago
|
||
s/2012/2014/
You need to log in
before you can comment on or make changes to this bug.
Description
•