Closed Bug 1381506 Opened 7 years ago Closed 7 years ago

stylo: "Resolving style on element without current styles" crash at [@ geckoservo::glue::Servo_ResolveStyle ]

Categories

(Core :: CSS Parsing and Computation, defect)

Product:
Core
Component:
CSS Parsing and Computation
Platform:
x86_64
Windows 10
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1381475

People

(Reporter: sciguyryan, Unassigned)

Details

(Keywords: crash)

Crash Data

Hi all!

I noticed the following crash on todays nightly - I had not seen this one before today. A quick search of the crash report system indicates that there seem to be quite a few, all of which originate from todays nightly build (17th of July 2017).

As of yet I have not been able to find a reproducible testcase for this but it seems to have started with a change between the last and current nightly (16th of July 2017 was fine, 17th of July 2017 isn't).
Crash Signature: [@ geckoservo::glue::Servo_ResolveStyle ]
Keywords: crash
Flags: needinfo?(xidorn+moz)
(In reply to Jan de Mooij [:jandem] from comment #1)
> Dupe of bug 1381475?

The stacks look a little different on this one: 37a74b27-2822-4b90-8f2d-fc3780170717 and this one ff7374bb-1cf4-41d5-be4a-30f770170717 and I honestly have no idea if they are two faces of the same problem or not. What do you think?
Yeah, after looking at this a bit more I think Jan is right here and this is a duplicate of bug 1381506. Marking as such!
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(xidorn+moz)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.