Closed
Bug 292923
Opened 19 years ago
Closed 19 years ago
crash forward/backward - Trunk [@ nsDocShell::FireRestoreEvents ]
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: Peter6, Assigned: bryner)
References
Details
(Keywords: crash, topcrash+)
Crash Data
Attachments
(1 file)
1.39 KB,
patch
|
bzbarsky
:
review+
bzbarsky
:
superreview+
brendan
:
approval-aviary1.1a1+
brendan
:
approval1.8b2+
|
Details | Diff | Splinter Review |
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050504 Firefox/1.0+ testing for bug 274784 settings: set browser.sessionhistory.max_viewers 10 set browser.history_expire_days 0 repro: 1.open FF 2.open forums and go back and forwards visiting threads 3. crash talkback TB5584080Q
Reporter | ||
Comment 1•19 years ago
|
||
->TB5584352Y to be precise open http://forums.mozillazine.org/viewforum.php?f=23 pick a thread , go forward an back (if needed a few times)
Reporter | ||
Comment 2•19 years ago
|
||
confirmed crash by others (via irc) settings set browser.sessionhistory.max_viewers 10 set browser.history_expire_days 9 still results in crashes set browser.sessionhistory.max_viewers 0 (off) fixes it
Depends on: blazinglyfastback
Comment 3•19 years ago
|
||
*** Bug 292926 has been marked as a duplicate of this bug. ***
Comment 4•19 years ago
|
||
You want bfcache (blazingly fast back, whatever) bugs in Core / Session: History and you want bryner cc'd at least. /be
Component: History → History: Session
Product: Firefox → Core
Updated•19 years ago
|
Blocks: blazinglyfastback
No longer depends on: blazinglyfastback
Comment 5•19 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050504 Firefox/1.0+ browser.sessionhistory.max_viewers = 50 browser.history_expire_days = 365 I think this might be adblock related. 1. Enable adblock 2. Go to slashdot.org 3. Pick an article 4. Go back -> crash Talkback looks the same as this ID's: TB5586455X TB5586413W TB5586150M TB5585973E TB5585395W TB5584429M (sorry I got trigger happy, won't submit any more TB for this issue, crashes occured on different sites) Repeat above with adblock disabled -> no crash
Comment 6•19 years ago
|
||
(In reply to comment #1) > ->TB5584352Y > > to be precise > open http://forums.mozillazine.org/viewforum.php?f=23 > pick a thread , go forward an back (if needed a few times) WFM (back and forward 22 times) set browser.sessionhistory.max_viewers 10 set browser.history_expire_days 1 Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.8b2) Gecko/20050505 Firefox/1.0+Beast
Reporter | ||
Comment 7•19 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050505 Firefox/1.0+ after some more testing: 1. I don't crash with a newly created profile (from scratch) 2. I don't crash with old profile, and extensions uninstalled 3. I DO CRASH with old profile, but extensions disabled
Assignee | ||
Updated•19 years ago
|
Assignee: nobody → bryner
Assignee | ||
Comment 8•19 years ago
|
||
Don't crash if there has never been a content viewer created (the about:blank viewer, which I thought was always present, turns out to be created lazily). Instead of bailing, I have it potentially create the content viewer here, just in case someone is listening for the DOMPageRestore event from this frame.
Attachment #182738 -
Flags: superreview?(bzbarsky)
Attachment #182738 -
Flags: review?(bzbarsky)
Comment 9•19 years ago
|
||
Comment on attachment 182738 [details] [diff] [review] patch So this is basically a frame in which we never did a load, right? If so, looks reasonable.
Attachment #182738 -
Flags: superreview?(bzbarsky)
Attachment #182738 -
Flags: superreview+
Attachment #182738 -
Flags: review?(bzbarsky)
Attachment #182738 -
Flags: review+
Assignee | ||
Comment 10•19 years ago
|
||
Right, in the adblock case it's a frame where the load was cancelled by nsIContentPolicy.
Assignee | ||
Comment 11•19 years ago
|
||
Comment on attachment 182738 [details] [diff] [review] patch requesting 1.1a approval
Attachment #182738 -
Flags: approval-aviary1.1a?
Reporter | ||
Comment 12•19 years ago
|
||
*** Bug 293074 has been marked as a duplicate of this bug. ***
Comment 13•19 years ago
|
||
Comment on attachment 182738 [details] [diff] [review] patch a=me. /be
Attachment #182738 -
Flags: approval1.8b2+
Attachment #182738 -
Flags: approval-aviary1.1a?
Attachment #182738 -
Flags: approval-aviary1.1a+
Updated•19 years ago
|
Keywords: topcrash+
Summary: crash forward/backward [ @ nsDocShell::FireRestoreEvents efa3d091 ] → crash forward/backward - Trunk [ @ nsDocShell::FireRestoreEvents efa3d091 ]
Assignee | ||
Comment 14•19 years ago
|
||
checked in
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 15•19 years ago
|
||
v.fixed per Talkback data, no crashes since 5/6
Status: RESOLVED → VERIFIED
Summary: crash forward/backward - Trunk [ @ nsDocShell::FireRestoreEvents efa3d091 ] → crash forward/backward - Trunk [ @ nsDocShell::FireRestoreEvents ]
Component: History: Session → Document Navigation
QA Contact: history → docshell
Severity: normal → critical
Summary: crash forward/backward - Trunk [ @ nsDocShell::FireRestoreEvents ] → crash forward/backward - Trunk [@ nsDocShell::FireRestoreEvents ]
Updated•13 years ago
|
Crash Signature: [@ nsDocShell::FireRestoreEvents ]
You need to log in
before you can comment on or make changes to this bug.
Description
•