Closed
Bug 1387490
Opened 7 years ago
Closed 7 years ago
stylo: _cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed
Categories
(Core :: Graphics, defect, P2)
Core
Graphics
Tracking
()
RESOLVED
DUPLICATE
of bug 1384701
| Tracking | Status | |
|---|---|---|
| firefox-esr52 | --- | unaffected |
| firefox55 | --- | unaffected |
| firefox56 | --- | wontfix |
| firefox57 | --- | affected |
People
(Reporter: jkratzer, Assigned: karlt)
References
(Blocks 2 open bugs)
Details
(Keywords: assertion, testcase)
Attachments
(1 file)
|
(deleted),
text/html
|
Details |
Attached testcase causes an assertion in m-c rev 36ad88e6b7b2 with stylo enabled by pref.
firefox: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed.
Exit code: -6
Flags: in-testsuite?
|
||
Comment 1•7 years ago
|
||
This looks like bug 1384701, but potentially does not require disabling e10s. Jason, can you confirm this was with e10s enabled?
Flags: needinfo?(jkratzer)
|
Reporter | |
Comment 2•7 years ago
|
||
(In reply to Bobby Holley (:bholley) (busy with Stylo) from comment #1)
> This looks like bug 1384701, but potentially does not require disabling
> e10s. Jason, can you confirm this was with e10s enabled?
This was identified with e10s disabled.
Flags: needinfo?(jkratzer)
Still good to have a fairly minimal testcase for this issue at least.
I have also noticed the e10s enabled variant happen in some DevTools test runs (mentioned in bug 1384701 comment 7).
|
||
Updated•7 years ago
|
Priority: -- → P2
|
|
||
Updated•7 years ago
|
Blocks: 1384701
status-firefox55:
--- → unaffected
status-firefox56:
--- → wontfix
status-firefox57:
--- → affected
status-firefox-esr52:
--- → unaffected
Summary: stylo: Assertion `hash_table->live_entries == 0' failed → stylo: _cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed
|
|
||
Comment 4•7 years ago
|
||
Karl is looking at this over in bug 1384701. Do I understand that this is the same bug, and just a testcase for it? Should we merge them?
Assignee: nobody → karlt
Flags: needinfo?(jryans)
(In reply to Bobby Holley (:bholley) (busy with Stylo) from comment #4)
> Karl is looking at this over in bug 1384701. Do I understand that this is
> the same bug, and just a testcase for it? Should we merge them?
Right, this is the same issue. I'll mark this as a duplicate and mention it in the other bug.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(jryans)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•