Closed
Bug 115787
Opened 23 years ago
Closed 23 years ago
"expedia.com" in page-loader crashes if ReconstructStyleData is used
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
RESOLVED
FIXED
mozilla0.9.8
People
(Reporter: jrgmorrison, Assigned: hyatt)
References
()
Details
Attachments
(1 file, 1 obsolete file)
(deleted),
patch
|
jag+mozilla
:
review+
waterson
:
superreview+
|
Details | Diff | Splinter Review |
Since this afternoon, the page-loader test on btek has been crashing while
loading the test copy of www.expedia.com. bryner and I have also reproduced
this in linux builds, and me in win32. On linux, it crashes on the first load
of that page, although on win2k, it actually made it through one complete
cycle before crashing again.
I'll attach stacks in a moment. bryner tried backing out waterson from this
afternoon, and that apparently didn't fix it. I am building without hyatt's
changes from this afternoon now and will see if that fixes it.
Reporter | ||
Comment 1•23 years ago
|
||
Assignee | ||
Comment 3•23 years ago
|
||
I have now fixed this by backing out my use of ReconstructStyleData in
StyleSheetAdded. I did leave my use of this function in StyleSheetRemoved,
which is called on a skin switch. So now we have reproducible crasher that will
happen on a skin switch, and I can work to figure out why ReconstructStyleData
can't be used everywhere.
Severity: blocker → critical
Status: NEW → ASSIGNED
Keywords: smoketest
Summary: page-loader crashes loading "expedia.com" in nsRuleNode → "expedia.com" in page-loader crashes on skin switch
Target Milestone: --- → mozilla0.9.8
Assignee | ||
Updated•23 years ago
|
Summary: "expedia.com" in page-loader crashes on skin switch → "expedia.com" in page-loader crashes if ReconstructStyleData is used
Comment 4•23 years ago
|
||
hyatt's change turned btek green, marking fixed.
Assignee | ||
Comment 5•23 years ago
|
||
I'm keeping this open to cover wanting to switch over to the better API. Don't
mark this fixed.
Assignee | ||
Comment 6•23 years ago
|
||
Attachment #62072 -
Attachment is obsolete: true
Comment 7•23 years ago
|
||
Comment on attachment 62133 [details] [diff] [review]
Avoid reframing when style sheets are added, style rules are added, or alternate stylesheets are enabled/disabled.
sr=waterson
Attachment #62133 -
Flags: superreview+
Comment 8•23 years ago
|
||
Comment on attachment 62133 [details] [diff] [review]
Avoid reframing when style sheets are added, style rules are added, or alternate stylesheets are enabled/disabled.
r=jag with the comment change in PresShell::StyleSheetRemoved
Attachment #62133 -
Flags: review+
Assignee | ||
Comment 9•23 years ago
|
||
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 10•23 years ago
|
||
So the first set of numbers off btek say that reductions for those pages that
had <style> elements in the body of the content:
avg. cached initial uncached
www.msn.com 114% 113%
www.expedia.com 126% 132%
www.cnn.com 121% 120% (which is almost 500 msec better)
The rest of the pages were neutral to favorable to this change.
Overall, about ~2.5% win. Nice!
Comment 11•23 years ago
|
||
This fix caused the regression bug 129350.
When a style sheet is added we need to reframe, at least that is the only thing
that makes sense to me. Otherwise, existing frames will have bogus style data,
based on the rules that were in the the old set of rules. Further analysis and
work in bug 129350
You need to log in
before you can comment on or make changes to this bug.
Description
•