Closed Bug 105172 Opened 24 years ago Closed 24 years ago

quote.yahoo.com crashes Mozilla 0.9.5 on Linux

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: slice1900, Assigned: asa)

References

()

Details

I visit quote.yahoo.com regularly, and have never had any problems with any version of Mozilla, including 0.9.5, until today. Apparently they changed something on the site, or some new ad is doing something funny, because I tried several times to access the site, and Mozilla crashed on me. This included trying to access it as the first and only site I went to after startup (I startup to a blank page) The browser just exited, there were no error messages listed to stdout/stderr as a result of the exit, and the fullcircle stuff didn't come up. I accessed quote.yahoo.com in Netscape 4.78 and it worked fine, and I did a 'save as...' of the current contents, on the chance that may be useful in case Yahoo fixes this site before anyone has a chance to look at this bug. Just let me know if that page will be useful and I can attach it to the bug report.
Well, I tried it today, and quote.yahoo.com didn't crash Mozilla. Nothing changed on my end, maybe they changed back whatever they changed, or their web server was temporarily insane and feeding me garbage when I was trying it yesterday. Probably ought to just resolve this as invalid to avoid wasting someone's time on this, I'll reopen it if the problem returns.
Tested as described with no crash using Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.5+) Gecko/20011016 Changed to Invalid as suggested.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
*** Bug 109509 has been marked as a duplicate of this bug. ***
I am seeing this again, using 0.9.5 for Linux. It doesn't happen every time, but if you go to quote.yahoo.com and hit shift-reload it'll happen eventually (it takes from 5-30 times in my testing) It sounds as though this bug may already be filed and assigned as bug 106322. Somewhat unrelated, but does anyone know why talkback is no longer enabled in any of the Linux builds? A couple milestones ago I used talkback once or twice to report crashers. If talkback Linux builds were still available, I'd have been able to nail down this bug a lot better much earlier.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
talkback is available in linux builds. The installer.tar.gz full install and the sea.tar.gz full install both install talkback. You can see if talkback is installec by looking in the install directory/components/talkback/
wfm using build 2001111706 on Linux.
unable to reproduce with 112002 linux 0.9.6 branch build.
WFM CVS 2001112617 Linux/x86. Could this be something related to the rotateing ads on their site? Mabey some java or activex ad is trying to load. See if you can get a copy of the page that does this, ethereal or one of those snoop-ware programs might beable to.
I wasn't ever able to get it to happen every day before, but I'd go to that page and have it crash every couple weeks. On a day that happened, it was reliably reproducible via shift-reload (5-30 times, as I noted before) But the next day it'd be gone. I've tried twice now to reproduce it with 0.9.6, with no success. If this doesn't recur by the time 0.9.7 is out, I'd say it was licked. I'm not quite ready to concede that yet, but I doubt anyone will raise any objections if this is closed. We can always reopen it if it happens again. I used the installer instead of the .tar.gz file to install 0.9.6, so I should get a talkback this time if it happens to me again.
0.9.7 is out soon. Any luck?
No news is good news, I think this may be licked. Go ahead and close it if you want, I'll reopen if it recurs (and hopefully include talkback info)
worksforme per reporter's comments. thanks for the follow-up
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.