Closed
Bug 628131
Opened 15 years ago
Closed 9 years ago
A content crash with a geolocation prompt open renders the browser unusable
Categories
(Firefox for Android Graveyard :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jdm, Unassigned)
Details
The "oops" dialog doesn't appear, and it becomes impossible to pan left or right on the current tab. If I turn my phone, I can sometimes see the tab bar, but the tabs won't close. I once got access to the JS console, and it was filled with messages about browser.getRootView being undefined.
Comment 1•15 years ago
|
||
Can you offer a way to reproduce a geolocation based crash, Josh?
Severity: normal → major
Priority: -- → P2
Comment 2•15 years ago
|
||
Also, what platforms are you seeing this crash on? Only desktop linux?
| Reporter | ||
Comment 3•15 years ago
|
||
This is on my galaxy s. I've been manually fuzz testing to see what happens when we crash, so I was just triggering a content crash via crashme-new.xpi or from a shell.
Mozilla/5.0 (Android; Linux armv71; rv2.0b13pre) Gecko/20110310 Firefox/4.0b13pre Fennec/4.0b6pre
Device: Droid 2
OS: Android 2.2
Not sure if this is relevent, there's an error that appears when using geolocation :
Error: Cc['@mozilla.org/wifi/monitor;1'] is undefined
Source File: resource://gre/components/NetworkGeolocationProvider.js Line: 257
When going to people.mozilla.com/~jmaher/wifi.html
I also reported https://bugzilla.mozilla.org/show_bug.cgi?id=613954#c22
when going to http://ie.microsoft.com/testdrive/HTML5/Geolocation/Default.html
| Reporter | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•