Nightly browser chrome hangs for about 10-20 seconds when editing text on Mana, Slack, Bugzilla
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox104 | --- | affected |
People
(Reporter: cpeterson, Unassigned)
References
Details
(Keywords: hang)
Today's Nightly has been hanging a lot for me today. I saw hangs when editing text in a Mana page, Slack, greenhouse.io, or Bugzilla. (I experienced the hang four times while entering this bug in Bugzilla.) The greenhouse.io hang happened while its text editor displayed a message saying it was auto-saving my draft text.
During a hang, both the browser chrome and content are unresponsive. To see if this was regression in today's Nightly, I installed a Nightly build from two days ago and still reproduced the hang. I installed a new Windows 11 Beta update last night, so that might be related, though the hangs only affect Nightly, not other apps.
Here are some profiles of hangs:
https://share.firefox.dev/3aOCRiJ
https://share.firefox.dev/3RMvSHv
https://share.firefox.dev/3yQlNka
|
Reporter | |
Comment 1•3 years ago
•
|
||
Tentatively moving this bug to the Disability Access APIs component because mozilla::a11y:AccessibleHandler functions show up in the profiles' stack traces during the hangs.
I'm running 64-bit Windows 11 Beta (Version 10.0.22622 Build 22622), if that matters. I've reproduced the hangs in both 32-bit and 64-bit Firefox.
|
|
Reporter | |
Comment 2•3 years ago
|
||
Bug 1774285 might be related. That bug mentions a Windows fix and, suspiciously, I started seeing these hangs after installing a Windows 11 Beta update. However, that bug says the Windows fix landed in the Dev Channel Ring and I'm running the Beta Channel Ring.
|
|
Reporter | |
Comment 3•3 years ago
•
|
||
I tested with the accessibility.force_disabled pref = 0 for ten minutes and didn't experience a hang. I disabled the pref, restarted Nightly, and almost immediately hit a hang when cutting/pasting text into Bugzilla.
I will re-enable accessibility and try testing with Windows clipboard's "Suggested Actions" disabled, as recommended in bug 1774285 comment 36.
|
||
Comment 4•3 years ago
|
||
For diagnostic purposes, would you mind also doing the steps in bug 1774285 comment 35?
|
|
Reporter | |
Comment 5•3 years ago
|
||
(In reply to James Teh [:Jamie] from comment #35)
- Open Edge.
- Copy some text, exactly as you would in Firefox to produce this problem.
- In the address bar, go to chrome://accessibility
- Under the Accessibility modes heading, what boxes are checked?
None of the accessibility mode boxes are checked.
- Under "View UIA Client", press the "Show client info" button. What info does it show, if any?
Nothing happens when I click the "Show Client Info" button. The "Name" and "Process ID" fields between the button still have the same - value.
|
|
Reporter | |
Comment 6•3 years ago
|
||
(In reply to Chris Peterson [:cpeterson] from comment #3)
I will re-enable accessibility and try testing with Windows clipboard's "Suggested Actions" disabled, as recommended in bug 1774285 comment 36.
I haven't experienced any Firefox hangs after I disabled Windows clipboard's "Suggested Actions" three hours ago. So it definitely seems related. Maybe this is a new Microsoft a11y bug.
|
|
||
Comment 7•3 years ago
|
||
I'm not sure why Edge can't detect this in your case, but given that disabling suggested actions fixes this for you, I'm fairly certain this is a dup of bug 1774285. It appears the bug has made it into the beta channel, as confirmed by multiple users in bug 1774285. The fix Microsoft is rolling out will land first on dev channel and should then make its way to beta.
We can reopen this if it turns out I'm wrong once the fix lands in Windows beta.
Description
•