Closed
Bug 861610
Opened 12 years ago
Closed 12 years ago
ASSERTION: Map should be empty already: 'clearedEntries == 0' running content/base/crashtests
Categories
(Core :: Layout: Text and Fonts, defect)
Core
Layout: Text and Fonts
Tracking
()
RESOLVED
FIXED
mozilla23
Tracking | Status | |
---|---|---|
firefox20 | --- | unaffected |
firefox21 | --- | fixed |
firefox22 | --- | fixed |
firefox23 | --- | fixed |
People
(Reporter: smontagu, Assigned: smontagu)
References
Details
(Whiteboard: [qa-])
Attachments
(1 file)
1.25 KB,
patch
|
ehsan.akhgari
:
review+
bajaj
:
approval-mozilla-aurora+
bajaj
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #861607 +++
With the patches from bug 861606 and bug 861607, running crashtests in content/base/crashtests still asserts:
REFTEST TEST-UNEXPECTED-FAIL | file:///home/smontagu/mozwork/hgtree/mozilla/content/base/crashtests/831287.html | assertion count 1 is more than expected 0 assertions
REFTEST TEST-UNEXPECTED-FAIL | file:///home/smontagu/mozwork/hgtree/mozilla/content/base/crashtests/849727.html | assertion count 1 is more than expected 0 assertions
Both assertions are:
ASSERTION: Map should be empty already: 'clearedEntries == 0', file /home/smontagu/mozwork/hgtree/mozilla/content/base/src/DirectionalityUtils.cpp, line 551
Assignee | ||
Comment 2•12 years ago
|
||
When we are setting dir to something other than auto, and the element has dirAutoSet, it must have had dir=auto before so we need to clear it from TextNodeDirectionalityMap.
Attachment #737219 -
Flags: review?(ehsan)
Updated•12 years ago
|
Attachment #737219 -
Flags: review?(ehsan) → review+
Assignee | ||
Comment 3•12 years ago
|
||
Flags: in-testsuite+
Comment 4•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
Assignee | ||
Comment 5•12 years ago
|
||
Comment on attachment 737219 [details] [diff] [review]
Patch
[Approval Request Comment]
Bug caused by (feature/regressing bug #): Bug 548206 or one of its followups
User impact if declined: without bug 861606 this could lead to sec-crit vulnerabilities. No such vulnerabilities are known at the time of writing, but they could probably be constructed as variations on earlier heap use after free bugs. With bug 861606 its impact is mitigated, but since risk is very low I'd like to get this in for the first release of dir=auto
Testing completed (on m-c, etc.): baked on m-c since 2013-04-15
Risk to taking this patch (and alternatives if risky): minimal
String or IDL/UUID changes made by this patch: none
Attachment #737219 -
Flags: approval-mozilla-beta?
Attachment #737219 -
Flags: approval-mozilla-aurora?
Updated•12 years ago
|
Attachment #737219 -
Flags: approval-mozilla-beta?
Attachment #737219 -
Flags: approval-mozilla-beta+
Attachment #737219 -
Flags: approval-mozilla-aurora?
Attachment #737219 -
Flags: approval-mozilla-aurora+
Assignee | ||
Comment 6•12 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/0d6b513a06a1
https://hg.mozilla.org/releases/mozilla-beta/rev/cc63217713dc
status-firefox20:
--- → unaffected
status-firefox21:
--- → fixed
status-firefox22:
--- → fixed
status-firefox23:
--- → fixed
Are there any user facing regression risks QA should be testing not covered by your tests?
Flags: needinfo?(smontagu)
You need to log in
before you can comment on or make changes to this bug.
Description
•