If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

browser reproducibly crashes on a certain website



13 years ago
12 years ago


(Reporter: Mikko Häkkinen, Unassigned)



Windows XP

Firefox Tracking Flags

(Not tracked)





13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803

My browser reproducibly crashes (tried 5 times) on the http://irc-galleria.net/
website. I was using Mozilla 1.7 when the bug occured, updated it to 1.7.2 and
the bug still remains with same results. I'm using Windows XP SP2. I have also
tried restarting which doesn't help. I haven't tried nightly builds.

The bug doesn't exist on Firebird (various versions), on IE (6), or on system
with Mozilla older than 1.7 and no XP SP2.

This is a bit problematic bug to verify because you have to register to the
website to be able to reproduce this. However, if you use IRC, you're entitled
to do so. You also can lie. :)

Reproduction process:
1. Log in under "Kirjautuminen" in the top left corner.
2. Search (nick) under "Haku" in the top right corner. Try "foo" for example.
3. Press brower's back button.
4. While loading the main page again the browser crashes.

Noticed things:
This doesn't work if you're not logged in. You have to use search. I'm unsure if
the search has to be successfull or does it happen when there are multiple
search results. You also have to search - otherwise returning to the main page
causes no problems.

P.S. I really am sorry if this bug has already been reported. This isn't easy
case to be searched from the bug database.

Reproducible: Always
Steps to Reproduce:
From the above:
1. Log in under "Kirjautuminen" in the top left corner.
2. Search (nick) under "Haku" in the top right corner. Try "foo" for example.
3. Press brower's back button.
Actual Results:  
From the above:
4. While loading the main page again the browser crashes.

Expected Results:  
The browser should have loaded the main page properly.

Comment 1

13 years ago
can you provide a talkback ID from the crash?

Comment 2

13 years ago
I definitely would like to, but where do you find one?

If you need registration instructions to the site, please drop me an email.

Comment 3

13 years ago
This is probably a dup of one of the following Mozilla bugs:
> I definitely would like to, but where do you find one?

Assuming you submitted the talkback report, just run components\talkback.exe and
you can read off the incident number.

Comment 5

13 years ago
Talkback ID is TB779972Z
Unfortunately that doesn't show symbols....  See

Comment 7

13 years ago
Another talkback id: TB806945H. My connention to the talkback-public.mozilla.org
is being refused so I can't verify it. :/

But this can be interesting information.

It seems that the browser doesn't seem crash if my network is lagging. This
could mean that the bug is somehow related to the ability to handle large
amounts of data quickly. Another clue is, that it can be related to loading
images, and perhaps also quickly comparing them to images in cache. This is what
I suppose because the images of the page I'm trying to load didn't load when it
was lagging - or they loaded very slowly.

Of course it's possible that it's my entire system which is being buggy, but I
doubt it because I updated my browser as I told in the previous messages.
Product: Browser → Seamonkey


13 years ago
Keywords: crash

Comment 8

13 years ago
Mikko Häkkinen: Are you still able to reproduce this bug with Mozilla Suite
1.7.6 or actual nightbuild?
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.