Closed
Bug 98435
Opened 25 years ago
Closed 24 years ago
Crash of when reloading xul page
Categories
(Core :: XUL, defect)
Tracking
()
VERIFIED
WORKSFORME
Future
People
(Reporter: dennishaney11, Assigned: hyatt)
References
()
Details
(Keywords: crash)
Attachments
(3 files)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3+) Gecko/20010905
When loading the page there is no problems, however a reload will crash mozilla.
Reproducible: Always
Steps to Reproduce:
1.load page
2.press reload
3.see moz crash
Actual Results: crash
Expected Results: reload of page
Happens at least in the last few days build, using gcc295 binaries...
gdb reports:
Program received signal SIGSEGV, Segmentation fault.
0x410d1f53 in NSGetModule () from /home/davh/mozilla/components/libgklayout.so
| Reporter | ||
Comment 1•25 years ago
|
||
Updated•25 years ago
|
Comment 2•25 years ago
|
||
confirming with win2k build 20010901.. (CVS debug)
| Reporter | ||
Comment 3•25 years ago
|
||
Fixed my server problem...
forgot to set correct Content-Type: application/vnd.mozilla.xul+xml ;(
Comment 4•25 years ago
|
||
| Reporter | ||
Comment 5•25 years ago
|
||
Comment 7•25 years ago
|
||
The crashing XUL is ...
<?xml version="1.0"?>
<?xml-stylesheet href="chrome://navigator/skin/" type="text/css"?>
<window align="vertical" xmlns:html="http://www.w3.org/TR/REC-html40"
xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"
class="dialog" >
<tree>
<treecolgroup>
<treecol>H
</treecol>
</treecolgroup>
<treehead>
<treerow>
<treecell label="A"/>
</treerow>
</treehead>
</tree>
</window>
and the key point is
<tree>
<treecolgroup>
<treecol>H <!-- um, don't do that -->
</treecol>
</treecolgroup>
Don't put a text node there. We don't deal with that.
Target Milestone: --- → Future
Comment 8•24 years ago
|
||
doesn't crash in a 10/12 win2k trunk build.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•