Android Fission Crash in [@ mozilla::a11y::IDSet::ReleaseID]
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
People
(Reporter: jonalmeida, Assigned: eeejay)
References
Details
(Keywords: crash, topcrash, Whiteboard: [fission:android:m2])
Crash Data
Attachments
(1 file)
Reported by a Reference Browser user here (but note that Fenix is also affected):
The crash happens when I have fission enabled, I'm using my galaxy tab s5e tablet os11 one ui 3.1 andriod in dex mode.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 1•2 years ago
|
||
That's a bit concerning. It suggests we're trying to unregister an id we already unregistered... or worse, we had an uninitialised id somehow. Eitan, any ideas?
Comment 2•2 years ago
|
||
123 out of 123 crash reports on Fenix Nightly 106 apparently have Fission enabled (by the user), which is surprising. In that case, I'll set status-firefox104 and status-firefox105 = disabled.
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
Also assure that unregistering an accessible removes the right one and
doesn't confuse the attached document with the detached one.
Comment 4•2 years ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 10 AArch64 and ARM crashes on nightly
:eeejay, could you consider increasing the severity of this top-crash bug?
For more information, please visit auto_nag documentation.
Comment 5•2 years ago
|
||
This is not a topcrash that is critical. It is a pref that nightly and beta users may enable. It is not a problem in release.
Comment 6•2 years ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 10 AArch64 and ARM crashes on nightly
:eeejay, could you consider increasing the severity of this top-crash bug?
For more information, please visit auto_nag documentation.
Comment 7•2 years ago
|
||
(In reply to Kevin Brosnan [:kbrosnan] from comment #5)
This is not a topcrash that is critical. It is a pref that nightly and beta users may enable. It is not a problem in release.
Comment 8•2 years ago
|
||
If we remove the topcrash
keyword, autonag will just add it back. If we leave the topcrash
keyword, autonag will complain that this "top" crash is should have a higher severity. So I'll just bump the severity from S3 to S2 to make autonag happy. Let's see if autonag complains that an S2 bug should have a higher priority.
Comment 10•2 years ago
|
||
bugherder |
Comment 11•2 years ago
•
|
||
Backed out for causing android gv-junit-fis-o crashes
Backout link: https://hg.mozilla.org/integration/autoland/rev/ab68ea19b50955d3de6e50e3692cfbda22b433ad
Updated•2 years ago
|
Comment 12•2 years ago
|
||
Comment 13•2 years ago
|
||
bugherder |
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Description
•