Closed Bug 1455005 Opened 6 years ago Closed 6 years ago

Intermittent thread '<unnamed>' panicked at 'Resolving style on <html> (0xa1e0880) without current styles: ElementData { styles: ElementStyles { primary: Some(Some(StrongRuleNode { p: 0xa18a760 })), pseudos: EagerPseudoStyles(None) }, damage:

Categories

(Core :: CSS Parsing and Computation, defect, P5)

defect

Tracking

()

RESOLVED INVALID

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure)

This was permafailing on debug for this push: https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=5cc1462548991de3dc524484f008e75394cb7df4&filter-resultStatus=retry&filter-resultStatus=usercancel&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=pending&filter-resultStatus=running&filter-resultStatus=success&filter-searchStr=crashtest

07:25:03     INFO - REFTEST TEST-START | file:///Users/cltbld/tasks/task_1524060785/build/tests/reftest/tests/layout/style/crashtests/1402366.html
07:25:03     INFO - REFTEST TEST-LOAD | file:///Users/cltbld/tasks/task_1524060785/build/tests/reftest/tests/layout/style/crashtests/1402366.html | 2891 / 3538 (81%)
07:25:03     INFO - ++DOMWINDOW == 129 (0x1124ef400) [pid = 1874] [serial = 8267] [outer = 0x121f0c800]
07:25:03    ERROR - thread '<unnamed>' panicked at 'Resolving style on <html> (0x121fe1d30) without current styles: ElementData { styles: ElementStyles { primary: Some(Some(StrongRuleNode { p: 0x12c4ee150 })), pseudos: EagerPseudoStyles(None) }, damage: GeckoRestyleDamage(nsChangeHint(0)), hint: RESTYLE_SELF | RESTYLE_DESCENDANTS, flags: TRAVERSED_WITHOUT_STYLING }', servo/ports/geckolib/glue.rs:4190:5
07:25:03     INFO - stack backtrace:
07:25:03     INFO -    0:        0x10f9c4483 - <std::sys::unix::backtrace::tracing::imp::UnwindError as core::fmt::Display>::fmt::h245d24052aeb872b
07:25:03     INFO -    1:        0x10f9bb8f2 - __rdl_shrink_in_place
07:25:03     INFO -    2:        0x10f9c11fd - std::panicking::Location::column::h1ba9cbe4f8116469
07:25:03     INFO -    3:        0x10f9c0e95 - std::panicking::Location::column::h1ba9cbe4f8116469
07:25:03     INFO -    4:        0x10f9c16e0 - std::panicking::rust_panic_with_hook::hfb431ab23831437f
07:25:03     INFO -    5:        0x10f9c14fe - std::panicking::begin_panic_fmt::h2d93f83eaf48dbcd
07:25:03     INFO -    6:        0x10f9c1452 - std::panicking::begin_panic_fmt::h2d93f83eaf48dbcd
07:25:03     INFO - Redirecting call to abort() to mozalloc_abort
07:25:03     INFO - Hit MOZ_CRASH() at /builds/worker/workspace/build/src/memory/mozalloc/mozalloc_abort.cpp:34
INVALID, then?
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
The changes were only frontend code and should only have triggered the issue, but the root cause still in the code base.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
That crashtest was added due to a very similar issue where the datetimepicker bindings (which are used for <input type="date">, etc.) added an UA sheet from layout.

Killing XBL is the fix, but meanwhile we'd need to figure out something to be able to land the patches in that bug. I don't think this bug is actionable on its own, not that there's particularly something to fix here. I could add a clearer assertion I guess.
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.