ANR on key event handling (/ key) in Firefox debug build
Categories
(Firefox for Android :: Browser Engine, defect)
Tracking
()
People
(Reporter: 2292776726, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:141.0) Gecko/20100101 Firefox/141.0
Steps to reproduce:
Possible reproduction steps (based on memory of the original occurrence — could not reproduce afterwards despite multiple attempts):
1.Have multiple pages open in Firefox debug build.
2.Open a Google page in Firefox debug build.
3.Tap menu.
4.Tap refresh.
5.Tap the address bar.
6.App becomes unresponsive (ANR).
I’m not sure what exactly caused the issue from my side as a user, but from the log it seems there may be additional details that could help with debugging.
ANR in org.mozilla.fenix.debug (org.mozilla.fenix.debug/.App)
PID: 18513
Reason: Input dispatching timed out (56e8e71 org.mozilla.fenix.debug/org.mozilla.fenix.debug.App (server) is not responding. Waited 5003ms for KeyEvent(deviceId=-1, eventTime=2060875000000, source=KEYBOARD, displayId=-1, action=DOWN, flags=0x00000008, keyCode=SLASH(76), scanCode=0, metaState=0x00000000, repeatCount=0), policyFlags=0x6b000000)
Actual results:
App becomes unresponsive (ANR).
Expected results:
UI responds immediately after refresh and address bar focus.
|
||
Comment 1•2 months ago
|
||
The severity field is not set for this bug.
:boek, could you have a look please?
For more information, please visit BugBot documentation.
|
||
Comment 2•2 months ago
|
||
Are you still able to reproduce this issue? Were you ever able to reproduce it on an official channel build (Nightly, Beta, Release)?
Hi Jeff,
I was not able to consistently reproduce this issue. I tried several times following the steps I initially reported, but it did not occur again. I have not tested it on the official channel builds (Nightly, Beta, Release), only on the debug build where it originally appeared.
Please let me know if you need any additional information or logs.
|
|
||
Comment 4•2 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox for Android::Browser Engine' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Description
•