fenix crashes - the menu freezes
Categories
(Firefox for Android :: Homepage, defect)
Tracking
()
People
(Reporter: emanuellclaudiu, Assigned: towhite)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [fxdroid])
Attachments
(4 files)
|
2.64 MB,
video/mp4
|
Details | |
|
[mozilla-mobile/firefox-android] Bug 1850480 - Revert "Upgrade navigation to latest version" (#3417)
59 bytes,
text/x-github-pull-request
|
Details | Review | |
|
59 bytes,
text/x-github-pull-request
|
dmeehan
:
approval-mozilla-beta+
|
Details | Review |
|
59 bytes,
text/x-github-pull-request
|
RyanVM
:
approval-mozilla-release+
|
Details | Review |
User Agent: Mozilla/5.0 (Android 11; Mobile; rv:109.0) Gecko/118.0 Firefox/118.0
Steps to reproduce:
- I entered "Settings".
- I went to "About Firefox".
- I quickly hit the back button to exit the main page.
- You may notice that the application crashes, cannot select the tab tray, cannot enter "Settings", etc.
It can also be reproduced on Firefox Nightly, Beta and Stable.
Actual results:
The application crashes, stops responding to commands.
Expected results:
The application should not crash and the buttons should work normally.
| Reporter | ||
Updated•2 years ago
|
| Reporter | ||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 1•2 years ago
|
||
:twhite tracking this across versions, have you confirmed the crash or have any idea of the regressor?
Updated•2 years ago
|
Comment 2•2 years ago
|
||
Looked into this and it can be reproduced. It looks like the regressor is the actual Navigation update from 2.5.3 to 2.6.0.
This can be reproduced by navigating to any sub-page of settings and then quickly pressing back 2 times to get to the browser fragment. At that point, the nav controller still has the settings fragment as a current destination, which is why navigating is not possible.
A simple workaround is to not quickly press the back button, or navigate to home after the navigation is broken, and continue using the app normally. Also, this does not crash and the app does not freeze in fact. Due to these reasons, I would suggest lowering the severity of this bug.
I have linked a Google IssueTracker with a similar STR ( wrong current destination after pressing back)
Comment 3•2 years ago
|
||
Comment 4•2 years ago
|
||
Comment 5•2 years ago
|
||
Comment on attachment 9350710 [details] [review]
[mozilla-mobile/firefox-android] Bug 1850480 - Revert "Upgrade navigation to latest version" (backport #3417) (#3418)
Beta/Release Uplift Approval Request
- User impact if declined: Navigation of the application from Settings will not work as expected
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: Follow procedure in bug details
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Reverting to the previously used navigation version
- String changes made/needed:
- Is Android affected?: No
Comment on attachment 9350706 [details] [review]
[mozilla-mobile/firefox-android] Bug 1850480 - Revert "Upgrade navigation to latest version" (backport #3417) (#3419)
Beta/Release Uplift Approval Request
- User impact if declined: Navigation of the application from Settings will not work as expected
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: Follow procedure in bug details
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Reverting to the previously used navigation version
- String changes made/needed:
- Is Android affected?: No
Comment 8•2 years ago
|
||
Updated•2 years ago
|
| Reporter | ||
Comment 10•2 years ago
|
||
Updated•2 years ago
|
Comment 11•2 years ago
|
||
Managed to reproduce the issue on an earlier Nightly build (118.0a1) and the current RC 117.0.
Verified as fixed on the current Nightly build (119.0a1 from 2023-08-30) and on the current Beta build (118.0b2).
Devices used:
- Google Pixel 7 (Android 14)
- Redmi 9C NFC (Android 10)
Marking the ticket as verified for 118 and 119.
Updated•2 years ago
|
Comment 12•2 years ago
|
||
Updated•2 years ago
|
Comment 13•2 years ago
|
||
Verified as fixed on the latest RC build (117.0.1).
Devices used:
- Google Pixel 7 (Android 14).
- Xiaomi Pad5 (Android 13).
- Lenovo tablet M10 (Android 10).
- Samsung Galaxy Tab A6 (Android 5.1).
Marking the ticket as verified for 117 as well.
Updated•2 years ago
|
Description
•