Closed
Bug 303904
Opened 19 years ago
Closed 19 years ago
Testcase using timers and then going back makes Mozilla crash [@ nsGlobalWindow::ResumeTimeouts]
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: martijn.martijn, Unassigned)
References
Details
(Keywords: crash, regression, testcase)
Crash Data
Attachments
(1 file, 1 obsolete file)
|
328 bytes,
text/html
|
Details |
See upcoming testcase.
You need to have fastback on to get the crash.
Regressed between 2005-07-19 and 2005-07-20:
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=2005-07-19+06%3A00%3A00&maxdate=2005-07-20+08%3A00%3A00&cvsroot=%2Fcvsroot
Maybe a regression from fixing bug 292890?
Talkback ID: TB8187699X
|
Reporter | |
Comment 1•19 years ago
|
||
|
|
Reporter | |
Comment 2•19 years ago
|
||
Oops, previous testcase was wrong.
Attachment #191975 -
Attachment is obsolete: true
|
||
Updated•19 years ago
|
Summary: Testcase using timers and then going back makes Mozilla crash → Testcase using timers and then going back makes Mozilla crash [ @ nsGlobalWindow::ResumeTimeouts]
|
||
Comment 3•19 years ago
|
||
I get also a crash, but only in an older build: <a
href="http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=TB8212729G">TB8212729G</a>
For me bfcache does not work anymore in the latest builds.
|
|
Reporter | |
Comment 4•19 years ago
|
||
This is WFM with 2005-08-19 trunk build.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Summary: Testcase using timers and then going back makes Mozilla crash [ @ nsGlobalWindow::ResumeTimeouts] → Testcase using timers and then going back makes Mozilla crash [@ nsGlobalWindow::ResumeTimeouts]
Component: History: Session → Document Navigation
QA Contact: history.session → docshell
|
Assignee | |
Updated•14 years ago
|
Crash Signature: [@ nsGlobalWindow::ResumeTimeouts]
You need to log in
before you can comment on or make changes to this bug.
Description
•