Closed
Bug 133164
Opened 23 years ago
Closed 23 years ago
Quickly hitting Back button several times causes crash
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 128933
People
(Reporter: reidr, Assigned: asa)
Details
(Keywords: crash, stackwanted)
I wanted to quickly go back several pages, so I hit the back button several
times in rapid succession, which caused mozilla to crash. (I don't really know
why I didn't just use the back history list....)
Using nightly from 20020319; I first saw it maybe a couple months ago. I've
since trained myself to not hit back multiple times.
Comment 1•23 years ago
|
||
Reporter, can you post Talkback ID when crashing ?
Run 'mozilla/components/talkback/talkback' to Talkback IDs.
Keywords: crash,
stackwanted
Reporter | ||
Comment 2•23 years ago
|
||
Okay, I ran the Linux installer to get a Talkback-enabled version, which I had
never done before. The Talkback ID is TB4425260Z.
In recreating the bug, I noticed that I couldn't get it to crash at Yahoo, for
example. It did happen when I descended several threads in the forums at
www.mozillazine.org. For example, go to "http://www.mozillazine.org/talkback/"
and pick a forum; then select a thread with multiple posts and click them in
turn. After that, hit back repeatedly and it should crash for you.
Comment 3•23 years ago
|
||
Just tried this with Win 98SE.
Talkback ID# TB4427817M
I'm also using 2002031903.
Comment 4•23 years ago
|
||
Confirming on Win2k. Changing OS to All. I don't know why someone would do
this, but the bug exists. Crash occured when I made it to the first loaded page.
Running 2002032408.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Comment 5•23 years ago
|
||
Also crashes in the exact same location while quickly hitting forward.
TB 4434523Z crash while hitting back
TB 4434886E crash while hitting forward
Build 2002032203 on Win2k.
I couldn't get it to crash on anything but mozillazine pages though.
Comment 6•23 years ago
|
||
I don't think that Mozillazine is the problem.
I got the same as what was mentioned in comment #4, where I got all the way back
to my first (i.e. Home) page and then the crash happened.
As for why someone would do this. I don't know either, but it is a problem which
might be indicative of something else that is wrong.
This bug happens to me as well, though I think in my case, it can happen at any
time I hit the back button; whether slow, fast, or in between. My talkback
incident IDs are:
TB4676829X
TB4481797G
TB4481409K
TB4481375W
All of these IDs are related to this bug. This is the only scenario that will
crash Mozilla on my machine. (A pretty good record, I'd say.)
If it matters, I'm running Mozilla build 2002031312 (The 0.9.9 milestone) on a
mostly default Slackware 8.0 system.
I've found a website which seems to cause a crash 100% of the time (eventually):
http://mini.net/tcl/0.html
Steps to reproduce:
1. Browse to the website above.
2. Follow any number of links inside it, staying within the /tcl tree. Fewer
than 10 clicks deep should be plenty.
3. Press the back button to attempt to return to the front page.
4. Notice Mozilla crash somewhere along the way.
Note that it might take a few tries, but the browser will eventually crash.
Comment 8•23 years ago
|
||
I used to be able to reproduce this 100% of the time, but I cannot get it to
crash with 2002032916.
Comment 9•23 years ago
|
||
Stack Signature 0x00000121 f424ac7f
Trigger Time 2002-03-24 15:35:33
Email Address reidr@bigfoot.com
URL visited http://www.mozillazine.org/
Build ID 2002032406
Product ID MozillaTrunk
Platform
Operating System LinuxIntel
Module
Trigger Reason SIGSEGV: Segmentation Fault: (signal 11)
User Comments I hit the back button multiple times while several levels deep
into a forum thread.
Stack Trace
0x00000121
StyleSetImpl::ResolveStyleFor()
nsPresContext::ResolveStyleContextFor()
FrameManager::ReResolveStyleContext()
FrameManager::ReResolveStyleContext()
FrameManager::ReResolveStyleContext()
FrameManager::ComputeStyleChangeFor()
PresShell::ReconstructStyleData()
PresShell::StyleSheetAdded()
nsDocument::InsertStyleSheetAt()
CSSLoaderImpl::InsertSheetInDoc()
CSSLoaderImpl::SheetComplete()
CSSLoaderImpl::ParseSheet()
CSSLoaderImpl::DidLoadStyle()
SheetLoadData::OnStreamComplete()
nsStreamLoader::OnStopRequest()
nsHttpChannel::OnStopRequest()
nsOnStopRequestEvent::HandleEvent()
nsARequestObserverEvent::HandlePLEvent()
PL_HandleEvent()
PL_ProcessEventsBeforeID()
processQueue()
nsVoidArray::EnumerateForwards()
nsAppShell::ProcessBeforeID()
handle_gdk_event()
libgdk-1.2.so.0 + 0x17d7f (0x4035cd7f)
libglib-1.2.so.0 + 0x11773 (0x40390773)
libglib-1.2.so.0 + 0x11d39 (0x40390d39)
libglib-1.2.so.0 + 0x11eec (0x40390eec)
libgtk-1.2.so.0 + 0x94333 (0x402ab333)
nsAppShell::Run()
nsAppShellService::Run()
main1()
main()
libc.so.6 + 0x1c6e7 (0x404ef6e7)
Comment 10•23 years ago
|
||
*** This bug has been marked as a duplicate of 128933 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•