Closed Bug 233120 Opened 21 years ago Closed 20 years ago

DNS: Failure leads to crash on close

Categories

(Core :: Networking, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: vimages, Assigned: darin.moz)

Details

(Keywords: crash, stackwanted)

Attachments

(1 file)

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

Scenario:

I retuned to the box this morning, and tried opening a few bookmarks. All were
unable to resolve DNS. Knowing this was commonly due to an intermittent failure
in my router, I started it rebooting.

I returned to the box, and tried again, using the same bookmarks that work. But,
the router handn't finished booting. DNS failures continued. So, I figured I'd
close the browser, and give it a breather.

Result: Hard crash, no talkback and just a simple modla dialog box. See attched
image of dialog

Reproducible: Couldn't Reproduce
Steps to Reproduce:
Attached image Error Dialog Box
-> Networking 
Assignee: general → darin
Severity: minor → critical
Component: Browser-General → Networking
Keywords: crash
QA Contact: general → benc
Is the network set up like this?

client -> router -> DNS server

What is the behavior of your router when it fails?

DNS is a pretty simple event model, so not much can go wrong when a router dies.
Yup. Simple home DSL machine. Static IP box (non-NAT) -> Netopia router -> DNS
servers at the ISP. The router just stops taking requests for anything external.
Solid lights, no indication of activity. I *can* reboot it remotely from the client.

I'd love to reproduce this, but.

I figured the error was off enough to make a bug worthwhile.
Yup. Simple home DSL machine. Static IP box (non-NAT) -> Netopia router -> DNS
servers at the ISP. The router just stops taking requests for anything external.
Solid lights, no indication of activity. I *can* reboot it remotely from the client.

I'd love to reproduce this, but.

I figured the error was odd enough to make a bug worthwhile.
This is one other report of DNS (still not behaving properly post-1.6a re-write.
I assume you were getting the usual "hostname not be found" error.

Unless there is talkback, I don't know if Darin can do anything about this problem.
Summary: DNS Failure leads to crash on close? → DNS: Failure leads to crash on close
Yes, classic "hostname not found" error

No, no talkback. Hard crash. 

I know it may not be "fixable", but good to know, nonetheless.
Jim, can you reproduce with Mozilla 1.7 beta which has talkback included? A
stack trace will probably be necessary to move this bug forward.
I'll give it a shot. It *was* pretty random. If not over the next week or so, we
can close as a WFM, or more accurately an "unable to reproduce". :)

-jim
Jim, did you reproduce it with Mozilla 1.7b or 1.7rc2 ?
Keywords: stackwanted
Nope. I'll close as WFM. I hate (my own) non-reproducble bugs. 
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
V.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: