use-after-poison in [@ mozilla::PresShell::ScrollFrameRectIntoView]
Categories
(Core :: Layout, defect, P3)
Tracking
()
People
(Reporter: tsmith, Assigned: TYLin)
References
(Blocks 2 open bugs)
Details
(4 keywords, Whiteboard: [post-critsmash-triage][adv-main66-])
Attachments
(5 files)
Reporter | ||
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
Comment 2•6 years ago
|
||
Comment 3•6 years ago
|
||
Comment 4•6 years ago
|
||
Comment 5•6 years ago
|
||
Comment 6•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Reporter | ||
Comment 8•6 years ago
|
||
Is it worth landing the crash test since bug 1445794 does not have one?
Assignee | ||
Comment 9•6 years ago
|
||
Yes, it's worth landing.
Even with bug 1445794, the test case still crashes with different stack because AccessibleCaretManager::DispatchCaretStateChangedEvent()
calls Selection::Stringify()
which flushes frames [1]...
Assignee | ||
Comment 10•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Comment 11•6 years ago
|
||
Updated•6 years ago
|
Comment 12•6 years ago
|
||
Verified on Nightly 67(20190129103321) and Beta 66.0b3(20190128143734), that the crash is not reproducible using the attached testcase.
Updated•6 years ago
|
Comment 13•6 years ago
|
||
(In reply to Ting-Yu Lin [:TYLin] (UTC-7) from comment #10)
The added crashtest still crashes on Android verify runs (TV) for
unknown reasons, so skip it.
Did anyone file a follow-up bug for this? If not, please do so
so we don't forget about it. (mark it security-sensitive just
in case, until we know what the issue is on that platform)
Assignee | ||
Comment 14•6 years ago
|
||
Mats, thank you for the reminder. Filed bug 1535187.
Updated•5 years ago
|
Description
•