Closed
Bug 316653
Opened 19 years ago
Closed 19 years ago
Crash [@ nsINodeInfo::GetDocument() line 269]
Categories
(Core :: XBL, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: bc, Unassigned)
References
Details
(Keywords: crash, Whiteboard: [sg:investigate])
Crash Data
I dont see that this is related to xform this rather a xbl issue
Reporter | ||
Comment 2•19 years ago
|
||
oops, I meant to send to xbl.
Assignee: aaronr → general
Component: XForms → XBL
QA Contact: spride → ian
Comment 3•19 years ago
|
||
This should _really_ not be happening (content without a nodeinfo). That said, on that page and with those settings I crash in a debug build while trying to reflow a fixed-position element, which is expected in a XUL document (see bug 253479).
Did you see any assertions before the crash happened (not neccesarily immideatly before)? I wonder if this could somehow happen during BindToDoc or some other place where we set mNodeInfo
Reporter | ||
Comment 5•19 years ago
|
||
(In reply to comment #4) Trying with a debug build from today I don't get this stack anymore, but get the stack from bug 316608. If I can't reproduce this stack, I will dupe it against 316608.
Updated•19 years ago
|
Summary: Crash [@ nsINodeInfo::GetDocument() line 269) → Crash [@ nsINodeInfo::GetDocument() line 269]
Comment 6•19 years ago
|
||
The backtrace looks like the one from bug 317265, maybe this is now fixed too with the fix for bug 317265?
Updated•19 years ago
|
Whiteboard: [sg:investigate]
Updated•19 years ago
|
Flags: blocking1.8.0.1?
Updated•19 years ago
|
Flags: blocking1.8.0.2?
Flags: blocking1.8.0.1?
Flags: blocking1.8.0.1-
Comment 7•19 years ago
|
||
Based on comment 5, marking as WFM.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Updated•19 years ago
|
Flags: blocking1.8.0.2? → blocking1.8.0.2-
Updated•17 years ago
|
Group: security
Updated•17 years ago
|
Flags: in-testsuite?
Updated•13 years ago
|
Crash Signature: [@ nsINodeInfo::GetDocument() line 269]
You need to log in
before you can comment on or make changes to this bug.
Comment 1
•