Closed
Bug 274791
Opened 20 years ago
Closed 20 years ago
crash [@nsIFrame::GetStyleData]
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 137216
People
(Reporter: csthomas, Unassigned)
References
()
Details
(Keywords: crash, testcase)
Crash Data
Attachments
(2 files)
To reproduce: 1. Visit URL http://ctho.ath.cx/tmp/mozcrash/test.xul 2. Click the "start" button, then "run" 3. The browser either crashes immediately, or asserts a few times and becomes unusable, and may subsequently crash (mrbkap seems to be experiencing this) When I crash, nsHTMLReflowState passed "null" for blockFrame to CalculateHypotheticalBox. aBlockFrame is null, but ->GetStyleVisibility doesn't crash directly until GetStyleData, which is trying to assert at http://lxr.mozilla.org/seamonkey/source/layout/generic/nsIFrame.h#611 but "this" is null, so accessing mStyleContext causes the crash. Filing unconfirmed as my testcase is far from minimized. Stack coming in a minute.
| Reporter | ||
Comment 1•20 years ago
|
||
| Reporter | ||
Comment 2•20 years ago
|
||
Some tracing by Callek found that http://lxr.mozilla.org/mozilla/source/layout/generic/nsHTMLReflowState.cpp#827 derefences aBlockFrame, even though http://lxr.mozilla.org/mozilla/source/layout/generic/nsHTMLReflowState.cpp#836 implies null is an expected value. The dereference can't be moved into the if(aBlockFrame) though, because it's used outside of the if later here (actually its only use): http://lxr.mozilla.org/mozilla/source/layout/generic/nsHTMLReflowState.cpp#888
Severity: normal → critical
Keywords: crash
Comment 3•20 years ago
|
||
Minimal testcase based on that site. This testcase doesn't crash for me in: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031030 But it crashes for me in: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208
aloha, a abs. pos. xul box that changes display type, boris likes this stuff ;-)
(In reply to comment #2) > even though > http://lxr.mozilla.org/mozilla/source/layout/generic/nsHTMLReflowState.cpp#836 > implies null is an expected value. More likely, it implies that whoever wrote the code believed that all pointers should be null-checked even when they should never be null.
| Reporter | ||
Comment 7•20 years ago
|
||
*** This bug has been marked as a duplicate of 137216 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
| Assignee | ||
Updated•13 years ago
|
Crash Signature: [@nsIFrame::GetStyleData]
You need to log in
before you can comment on or make changes to this bug.
Description
•