Closed
Bug 1330092
Opened 8 years ago
Closed 4 years ago
Gecko might fail to (re)load properly if an external tab arrives just as the UI is closing
Categories
(Firefox for Android Graveyard :: General, defect, P5)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: JanH, Unassigned)
References
Details
Attachments
(1 file)
(deleted),
text/plain
|
Details |
STR:
1. Connect device to PC via ADB
2. Make sure the Firefox variety you're testing this with is the default handler for opening web links.
3. Enable the "Quit" menu item by setting any of the options in Settings -> Privacy -> Clear private data on exit
4. Have Firefox's main menu open and be ready to press the "Quit" button.
5. From a command line on the PC run |adb shell am start -a android.intent.action.VIEW -d https://bugzilla.mozilla.org|
6. Quit Firefox.
Expected:
Depending on your timing, either the UI opens a new tab and then close, or else it should close and then immediately restart with the new tab.
Actual:
If you get the timing just right, the UI will close, then open again to process the incoming intent, however Gecko will fail to start up correctly, so instead of a web page, you're just looking at white space. Logcat will probably also show some related error messages. The Java UI itself might also lock up in some way.
Notes:
- You need to play a bit around with the timing of 5. and 6. - there'll probably be a slight delay between sending the intent on the command line and it being received by Firefox. Ideally, you'll want the intent to arrive just after you've hit the "Quit" button.
- Enabling session store debug logging (flip browser.sessionstore.debug_logging in about:config and restart) might be helpful to see the various shutdown notifications on the Gecko side.
Reporter | ||
Comment 1•8 years ago
|
||
Actually just now, after the UI had locked up and I had switched to the home screen, I had to manually force quit Fennec (no ANR message) in order to be able to start it up again - tapping the launcher icon didn't do anything, not even a white screen.
Comment 2•6 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
Reporter | ||
Updated•6 years ago
|
Status: RESOLVED → REOPENED
Resolution: INACTIVE → ---
Reporter | ||
Updated•6 years ago
|
Status: REOPENED → NEW
Comment 3•6 years ago
|
||
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195
Needinfo :susheel if you think this bug should be re-triaged.
Priority: -- → P5
Comment 4•4 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 6 years ago → 4 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•