Closed
Bug 448503
Opened 16 years ago
Closed 16 years ago
Crash [@ no stack] on reloading with mathml, xbl and ordinal attribute
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: martijn.martijn, Unassigned)
References
Details
(Keywords: crash, regression, Whiteboard: [sg:dupe 431705])
Crash Data
Attachments
(1 file, 1 obsolete file)
|
(deleted),
application/vnd.mozilla.xul+xml
|
Details |
See testcase, which usually crashes after reload.
I don't get a useful stack at all with the testcase.
See for example: http://crash-stats.mozilla.com/report/index/a2a23126-5e12-11dd-bd67-001a4bd43e5c?p=1
0 @0x7d702fb
This seems to have regressed between 2008-02-18 and 2008-02-19:
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2008-02-18+04&maxdate=2008-02-19+09&cvsroot=%2Fcvsroot
Regression from bug 399852 perhaps? Or from bug 417699?
|
||
Comment 1•16 years ago
|
||
So far no luck with reproducing this.
|
Reporter | |
Comment 2•16 years ago
|
||
Ok, maybe the reload timer was a bit too quick.
Attachment #331712 -
Attachment is obsolete: true
|
||
Comment 3•16 years ago
|
||
On the 1.9.0 branch (cvs head) this now WFM. Crashes on a 2008-12-15-05 build, no longer crashes on a 2008-12-18-06 build (WinXP). Most likely fix might be Mats's patch for bug 431705, or maybe bug 401042.
qawanted: please retest in Shiretoko and if fixed either close WFM or if mats/roc agrees dupe to the appropriate bug.
Keywords: qawanted
Whiteboard: [sg:critical?]
|
|
Reporter | |
Comment 4•16 years ago
|
||
Yeah, probably fixed by bug 431705.
|
||
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
|
|
||
Updated•15 years ago
|
Group: core-security
|
Assignee | |
Updated•13 years ago
|
Crash Signature: [@ no stack]
|
||
Comment 5•10 years ago
|
||
Issue is Resolved - removing QA-Wanted Keywords - QA-Wanted query clean-up task
You need to log in
before you can comment on or make changes to this bug.
Description
•