After an attempt to access http://www.geom.umn.edu/locate/qhull stalled interminably "trying to resolve..." I removed the "www." and added a trailing "/". Attempts to access the URL which resulted crashed Mozilla, and crashed it again when I brought up a fresh launch of Mozilla with a blank starting page. The talkback session ID for the first crash may have been TB3068067Y, and may have reached your feedback address, but as talkback itself also crashed trying to transmit the data, I'm not sure of either, the talkback window didn't repaint when I went back to read the second part of the session ID. The Windows 98b illegal instruction widget gave these details, for Mozilla build ID 2001051704: MOZILLA caused a stack fault in module JS3250.DLL at 017f:60c92a52. Registers: EAX=02602e20 CS=017f EIP=60c92a52 EFLGS=00010202 EBX=00592174 SS=0187 ESP=00592000 EBP=0059201c ECX=008a6730 DS=0187 ESI=02432200 FS=4e77 EDX=02602e20 ES=0187 EDI=008a6730 GS=0000 Bytes at CS:EIP: 56 8b 74 24 08 8b 02 8b 48 04 81 f9 b0 54 cd 60 Stack dump: 600c48d5 02432200 02602e20 008a6730 02432200 00592174 008a6730 00592038 600c495a 02432200 02602e20 00592174 00000000 60c9c689 00592074 600c4999

I guess this is a dup of bug 81273.

Probably a duplicate, yes, since the site comes up fine when the server is live. Don't have a handy dead server to check if a crash still occurs, so cannot mark it "WORKSFORME" but this bug should probably go away as a dup, so I'm doing that. *** This bug has been marked as a duplicate of 81273 ***

qa to me. VERIFIED: Kent, reopen this if this happens in builds after the target duplicate was fixed. You can probably find other public URL's in those duplicates to test.

Ben, I'd be happy to help, but your terminology baffles me. What is a "target duplicate"? Is this "fix" you are speaking of something in the past (already done) or in the future (how do I know when it happens)? "Public URLs" where?

This bug was marked a duplicate of 81273, which is marked fixed. Look in that bug to find out which build you can download that is fixed. Then test for the problem again. That bug has many other duplicates tagged to it. Some of them probably contain URL's that are visible on the "public network" (the unrestricted sections of the Internet we surf), so see if you can get the problem to happen...

I managed to get lucky and confirm the fix an easier way; apparently that server goes offline regularly every night about the time I'm just getting warmed up (4AM), and attempting to access the reference URL when the site is down now brings up a "connection refused" message box rather than crashing Mozilla. Thanks for the fix!