Closed
Bug 836074
Opened 13 years ago
Closed 12 years ago
[crash reporting] Banner for firefox os crashing/sending report disappears too quickly (appears for only ~ 2 seconds)
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 826380
People
(Reporter: nhirata, Unassigned)
References
Details
Attachments
(1 file)
|
87.17 KB,
image/png
|
Details |
## Environment :
Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/b9871d06ba06
Gaia 03401aa0cedac9bc8332e1342aac274a62f4416f
BuildID 20130129070201
Version 18.0
Unagi
## Repro :
1. flash device
2. do not select "I want to help improve Firefox OS " when going through FTE
3. go to settings -> Improve Firefox OS
4. verify that "Ask me when a crash occurs" is selected
5. kill -11 b2g process.
6. go into the /data/b2g/mozilla/Crash Reports folder
## Expected :
Once the phone is fully booted, the submit report dialog should appear.
## Actual :
there's a small banner that appears that says Firefox crashed with a "Report" box that's clickable. But it only lasts a short time while on the splash screen. I would guess about 2 second display?
## Note :
| Reporter | ||
Updated•13 years ago
|
Component: Networking → General
Product: Core → Boot2Gecko
Version: 18 Branch → unspecified
Comment 1•13 years ago
|
||
Dupe of Bug 826380?
| Reporter | ||
Comment 2•13 years ago
|
||
It's a difference between OS crash and App Crash.
Personally I don't think we should have an OS crash banner... it just seems silly considering you see the whole thing reboot.
I'll leave it to lco to dup... Original I filed this bug to note that I wasn't getting the dialog. turned out that this was occuring on the master. Not sure if that's a valid bug...
v1.0.0 is working fine... master branch isn't working right...
Comment 3•12 years ago
|
||
It is the same bug as the code path is the same. What you call "OS Crash" is just a Gecko crash, like an App Crash is a Gecko crash.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•