Closed
Bug 1379019
Opened 8 years ago
Closed 8 years ago
stylo: site issue: tab crash [@ nsCSSFrameConstructor::FindFrameForContentSibling ] on youtube.com
Categories
(Core :: CSS Parsing and Computation, defect, P1)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jan, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: nightly-community)
Crash Data
Attachments
(2 files)
Nightly 56 x64 20170706130309 @ Debian Testing (Linux 4.9.0-3-amd64, Radeon RX480)
I am unsure if this is a stylo bug,
but it happend while watching https://www.youtube.com/watch?v=PdGSBeZPoRo
and I saw mozilla::ServoRestyleManager::DoProcessPendingRestyles
in bp-21c9f7ab-867a-4dfc-b0e5-8d7aa0170706.
At this time I also had
gfx.webrender.enabled;true
gfx.webrendest.enabled;false
but resetted them after the tab crash. Later I got bug 1379018.
I don't know if this might be relevant, but I am testing extensions.webextensions.remote;true since today (bug 1357487 comment 4).
Reporter | ||
Updated•8 years ago
|
Reporter | ||
Comment 1•8 years ago
|
||
No it can also happen without webrender+webrendest+OOPwebextensions.
bp-0c523c28-e1ca-4ec7-807d-0c4f30170706.
I should try this with a clean profile tomorrow. Or with that debug build from bug 1378064 comment 6 where I learned how to get RUST_LOG=debug.
Reporter | ||
Comment 2•8 years ago
|
||
This happend between the two reported crash signatures: the red video progress bar is missing. I can't reproduce this.
Reporter | ||
Comment 3•8 years ago
|
||
Then I wanted to leave fullscreen and ended like that. I switched to another tab, came back, got the e10s loading circle and then I closed the whole browser.
After starting Nightly again, I found bp-b890844a-8440-41e6-97f6-246720170706 [@ IPCError-browser | ShutDownKill ] on about:crashes.
This seems a bit like bug 137806 vice versa and bug 1377739.
Reporter | ||
Comment 4•8 years ago
|
||
correction:
> This seems a bit like bug 1378064 [...]
Reporter | ||
Updated•8 years ago
|
Crash Signature: [@ nsCSSFrameConstructor::FindFrameForContentSibling ]
Comment 5•8 years ago
|
||
I see APZ from the stack. This may be related to bug 1371450 as well I guess.
Updated•8 years ago
|
Priority: -- → P1
Reporter | ||
Comment 6•8 years ago
|
||
Last crash with Build 20170716100258 so far.
Comment 7•8 years ago
|
||
Sure, let's close this.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•