Closed
Bug 1379617
Opened 7 years ago
Closed 7 years ago
stylo: Crash in nsIFrame::SetNextSibling
Categories
(Core :: CSS Parsing and Computation, defect, P1)
Tracking
()
RESOLVED
FIXED
mozilla56
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox54 | --- | unaffected |
firefox55 | --- | unaffected |
firefox56 | --- | fixed |
People
(Reporter: marcia, Assigned: heycam)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
This bug was filed from the Socorro interface and is
report bp-a8141646-372b-40d9-84da-e6d630170710.
=============================================================
55 crashes/16 installs that have stylo enabled (at least the 6 reports I spot checked): http://bit.ly/2tG1O5U
Not sure who to need info, is it bholley?
Updated•7 years ago
|
Blocks: stylo-site-issues
Comment 1•7 years ago
|
||
My guess is that the frame constructor somehow messes things up, and we end up violating this assertion: https://hg.mozilla.org/mozilla-central/file/06c1a0dc0fd8/layout/generic/nsFrameList.cpp#l90
Not sure what happens behind, though, since there is no reproducible steps...
Updated•7 years ago
|
Priority: -- → P1
Comment 2•7 years ago
|
||
I had this crash to twice in the last days.
I can only remember one crash partly and there the tab crashed in a JIRA Case ticket (e.g. https://MY-SYSTEM.atlassian.net/browse/ABC-4901). I think I just tried to open or close an image, but I'm not sure.
Comment 3•7 years ago
|
||
I can trigger this bug by opening and closing popup image, and scrolling the page between. It result in page visual glitch and tab crashes soon after. It is quite rare, so it is hard to provide exact steps to reproduce.
But I also hit bug 1379218 crash while doing my test, so they might have the same cause.
Comment 4•7 years ago
|
||
I can hit this crash pretty often when editing the general review comment in mozreview.
Comment 5•7 years ago
|
||
Please note that there is also bug 1381475 which gets triggered by review comments in mozreview. Are both crashes somehow related?
I can trigger this bug easily with the following steps:
1. Go to https://www.youtube.com/testtube and sign up for the Material design beta
2. Browse some videos, in a few minutes you will get a crash with this bug
Assignee | ||
Comment 8•7 years ago
|
||
(In reply to Grant from comment #6)
> 1. Go to https://www.youtube.com/testtube and sign up for the Material
> design beta
> 2. Browse some videos, in a few minutes you will get a crash with this bug
Hi Grant, can you clarify the STR for me? Do I need to click Sign Up, and go through the lengthy questionnaire where I provide Google with my details for their UX researches to contact me? Or it it just the "Try new YouTube" button on youtube.com/testtube that I need (which has a Material Design logo next to it)?
Flags: needinfo?(tenisthenewnine)
Comment hidden (typo) |
Comment hidden (typo) |
Assignee | ||
Comment 11•7 years ago
|
||
I haven't had any luck reproducing this so far, but I see that the aren't any reports of this crash on crash-stats after the 20170716030208 build.
Comment 12•7 years ago
|
||
I could assume that this is maybe overlayed by bug 1381475? If that assumption is true we should see the signature again very soon.
Assignee | ||
Comment 13•7 years ago
|
||
Yes, that might be it. Let's see if it crops up again with today's nightly.
Comment 14•7 years ago
|
||
No longer happened since 20170716030208. I think this crash also has been fixed by bug 1371450. Waiting for a reply from Grant a couple of more days.
Comment 15•7 years ago
|
||
Though we have no reply from Grant yet, we haven't received new crash reports since 20170716030208 build. Closing.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Target Milestone: --- → mozilla56
Updated•7 years ago
|
status-firefox54:
--- → unaffected
status-firefox55:
--- → unaffected
status-firefox-esr52:
--- → unaffected
You need to log in
before you can comment on or make changes to this bug.
Description
•