Closed
Bug 73890
Opened 25 years ago
Closed 24 years ago
Bad: crashes loading any www page
Categories
(Core :: Networking, defect)
Tracking
()
VERIFIED
WORKSFORME
mozilla1.0
People
(Reporter: adamc, Assigned: neeti)
Details
(Keywords: crash)
Attachments
(2 files)
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
BuildID: 2001032319
Mozilla crashes when loading any www page for me. Talkback id TB28393380H.
Reproducible: Always
Steps to Reproduce:
1.Load mozilla
2.goto www site
3.crash
http://lxr.mozilla.org/seamonkey/source/netwerk/dns/src/nsDnsService.cpp#1584
http://bonsai.mozilla.org/cvsblame.cgi?
file=mozilla/netwerk/dns/src/nsDnsService.cpp#1584
Comment 1•25 years ago
|
||
nsDNSService::AllocMsgID
[d:\builds\0.8.1\mozilla\netwerk\dns\src\nsDnsService.cpp, line 1592]
nsDNSLookup::InitiateLookup
[d:\builds\0.8.1\mozilla\netwerk\dns\src\nsDnsService.cpp, line 585]
nsDNSLookup::Resume
[d:\builds\0.8.1\mozilla\netwerk\dns\src\nsDnsService.cpp, line 730]
nsDNSLookup::HandleRequest
[d:\builds\0.8.1\mozilla\netwerk\dns\src\nsDnsService.cpp, line 496]
nsDNSService::Lookup
[d:\builds\0.8.1\mozilla\netwerk\dns\src\nsDnsService.cpp, line 1326]
nsSocketTransport::doResolveHost
[d:\builds\0.8.1\mozilla\netwerk\base\src\nsSocketTransport.cpp, line 609]
<http://cyclone/images/spacer.gif>
Comment 2•25 years ago
|
||
That is fugly code there...checked in Version 1.45 by gordon.
Comment 3•25 years ago
|
||
-> Netowrking
Assignee: asa → neeti
Component: Browser-General → Networking
QA Contact: doronr → tever
www.betanews.com
www.voodooextreme.com
www.anandtech.com
www.tomshardware.com
and others. Sometimes crashes going from one to another.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Comment 8•25 years ago
|
||
How is a crash in DNS related to a (relatively benign) failure to fire onload?
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
I can't reproduce this on Windows NT 4.0.1381. Asa, we're you able to reproduce
this, or did you did the stack trace out of the talkback data?
Adam, does this still happen for you? nsDNSService::AllocMsgID hasn't been
touched in over a year. It's not clear how it could crash, unless the the
nsDNSService itself was somehow corrupted.
Comment 10•25 years ago
|
||
Reporter:
Can you try it again with a new profile ?
(run "mozilla -profilemanager")
Comment 11•25 years ago
|
||
The stacktrace is what I pulled out ot Talkback. Sorry for the confusion. I am
not able to reproduce this on any platform (including win2K)
| Reporter | ||
Comment 12•25 years ago
|
||
Yes I tried a new profile, does the same thing. Tried re-installing several
times (each time wiping all traces of Mozilla). I can send anyone who wants it
a copy of my crash log (dr watson) and talkback log if that would help, just e-
mail me and ask.
Comment 13•25 years ago
|
||
Has anyone beside Adam been able to reproduce this, or heard rumors of others
being able to reproduce it?
Asa, do we have other talkback reports of this crash?
Comment 14•25 years ago
|
||
I can´t reproduce it with win2k build 20010408.. (CVS)
Reporter: Are you using a proxy or other special settings ?
(Have you a SMP machine ? Have you Win2k Professional or server ?..)
Can you try it with a a new build ?
Have you write access to any directorys.(Please try it as Admin/root)
Can you try to delete c:\winnt\mozregistry.dat.
| Reporter | ||
Comment 15•25 years ago
|
||
I'm running behind a NAT based firewall, one gateway setting in my TCP/IP
settings does the trick. I do not have an SMP machine. Win 2k Pro SP1. I've
tried new builds, old builds, all do the same thing. I am logged in as Admin.
When I say I wipe mozilla when I do a re-install I also delete the
mozregistry.dat file, yes.
Comment 16•25 years ago
|
||
godron, the reporter included the top of the stack and the incident ID of the
talkback report in his original comment. In my first comment in the bug I
pasted the stack trace from that talkback report into the bug.
| Assignee | ||
Comment 17•25 years ago
|
||
I am unable to reproduce the crash for all the sites reported above on win NT
4.0
Comment 18•25 years ago
|
||
I can´t reproduce it with win2k. I use also NAT for my connection (Windows 2k
ICS -> Internet Connection Sharing)
| Reporter | ||
Comment 19•25 years ago
|
||
To anyone who cannot reproduce this bug I'll send you a copy of my talkback and
dr watson log of it crashing, to show you I'm not insane, really :) I'm just
trying to figure out WTF is going on...PS I also tried Netscape 6.x awhile back
and it did the exact same thing, if that helps.
Comment 20•25 years ago
|
||
adam: please attach those logs to this bug, thx!
| Reporter | ||
Comment 21•25 years ago
|
||
| Reporter | ||
Comment 22•25 years ago
|
||
| Reporter | ||
Comment 23•25 years ago
|
||
Ok they're attached.
Comment 25•24 years ago
|
||
Reporter: Is this a problem with a new build ?
Can you poste a new Talkback ID (many network code changed) ?
| Reporter | ||
Comment 26•24 years ago
|
||
Hey sorry about the delay in reply, I haven't tried the latest build yet, I
will do so today and report.
Comment 27•24 years ago
|
||
adamc@rochester.rr.com: Is this now fixed ?
| Reporter | ||
Comment 28•24 years ago
|
||
Well I re-loaded my machine (not because of this problem) and that seemed to
help, also am running 9.3 now and it doesn't crash as often however visiting 4-
5 sites in a row will still crash on the last one, say 3 out of 5 times. Let
me know who to send the log of it's crashing too and they can tell me if it's
related or not. Thanks!
Comment 29•24 years ago
|
||
adamc, can you please reproduce this crash a few times and send in those
talkback reports with a comment "bug 73890" and then post the Talkback IDs here
in this bug. thanks.
Comment 30•24 years ago
|
||
still happening? REOPEN if it does... otherwise marking as WFM
Status: REOPENED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → WORKSFORME
Comment 31•23 years ago
|
||
VERIFIED:
adamc, please reopen if this happens w/ mozilla 1.2.1 or later.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•