Closed
Bug 258845
Opened 20 years ago
Closed 19 years ago
browser reproducibly crashes on a certain website
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: mchaka, Unassigned)
References
()
Details
(Keywords: crash)
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.
Reporter | ||
Comment 2•20 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•20 years ago
|
||
This is probably a dup of one of the following Mozilla bugs: http://bugzilla.mozilla.org/show_bug.cgi?id=103975 http://bugzilla.mozilla.org/show_bug.cgi?id=255933 http://bugzilla.mozilla.org/show_bug.cgi?id=87842
Comment 4•20 years ago
|
||
> 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.
Reporter | ||
Comment 5•20 years ago
|
||
Talkback ID is TB779972Z
Comment 6•20 years ago
|
||
Unfortunately that doesn't show symbols.... See http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=TB779972Z
Reporter | ||
Comment 7•20 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.
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 8•19 years ago
|
||
Mikko Häkkinen: Are you still able to reproduce this bug with Mozilla Suite 1.7.6 or actual nightbuild?
Comment 9•19 years ago
|
||
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/
Comment 10•19 years ago
|
||
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•