Closed
Bug 588794
Opened 14 years ago
Closed 14 years ago
Conditional jump or move depends on uninitialised value(s) [@ CSSLoaderImpl::ParseSheet]
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
status2.0 | --- | unaffected |
blocking1.9.2 | --- | - |
status1.9.2 | --- | .11-fixed |
blocking1.9.1 | --- | - |
status1.9.1 | --- | .14-fixed |
People
(Reporter: MatsPalmgren_bugz, Assigned: MatsPalmgren_bugz)
References
Details
(Keywords: regression, valgrind, Whiteboard: [qa-examined-192] [qa-examined-191])
Attachments
(2 files)
4.00 KB,
text/plain
|
Details | |
1.79 KB,
patch
|
dbaron
:
review+
dveditz
:
approval1.9.2.11+
dveditz
:
approval1.9.1.14+
|
Details | Diff | Splinter Review |
Conditional jump or move depends on uninitialised value(s) [@ CSSLoaderImpl::ParseSheet]
Affects 1.9.2 and 1.9.1, not trunk
Assignee | ||
Comment 1•14 years ago
|
||
The typo fix is to make -DDEBUG_TRACEMALLOC_PRESARENA compile.
Attachment #467432 -
Flags: review?(dbaron)
Comment on attachment 467432 [details] [diff] [review]
fix
r=dbaron
Attachment #467432 -
Flags: review?(dbaron) → review+
This seems like something that could break any chrome style sheets that have a syntax error in the first rule, which could be a problem for some extensions. Seems like something we should get in to the branch soon.
It's a regression from bug 524223.
This would not block a release, but we would like to fix it as it is a regression. Feel free to nominate for for 3.6.10 and 3.5.13 when it is ready.
blocking1.9.1: ? → -
blocking1.9.2: ? → -
status1.9.1:
--- → wanted
status1.9.2:
--- → wanted
Keywords: regression
Assignee | ||
Updated•14 years ago
|
Attachment #467432 -
Flags: approval1.9.2.10?
Attachment #467432 -
Flags: approval1.9.1.13?
Comment 5•14 years ago
|
||
Comment on attachment 467432 [details] [diff] [review]
fix
Approved for 1.9.2.10 and 1.9.1.13, a=dveditz for release-drivers
Attachment #467432 -
Flags: approval1.9.2.10?
Attachment #467432 -
Flags: approval1.9.2.10+
Attachment #467432 -
Flags: approval1.9.1.13?
Attachment #467432 -
Flags: approval1.9.1.13+
status2.0:
--- → unaffected
Assignee | ||
Comment 6•14 years ago
|
||
http://hg.mozilla.org/releases/mozilla-1.9.2/rev/bc021a2ec6a9
http://hg.mozilla.org/releases/mozilla-1.9.2/rev/2e3179e393e3
http://hg.mozilla.org/releases/mozilla-1.9.1/rev/05acd6e91c43
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 7•14 years ago
|
||
Is there anything for QA to do to verify this on branch?
Whiteboard: [qa-examined-192] [qa-examined-191]
Assignee | ||
Comment 8•14 years ago
|
||
(In reply to comment #7)
> Is there anything for QA to do to verify this on branch?
Probably not, you need a special build (ac_add_options --enable-valgrind)
and then run unit tests under valgrind to see the reported error.
Maybe it's possible to make a testcase based on comment 3, I don't know.
You need to log in
before you can comment on or make changes to this bug.
Description
•