Closed Bug 224754 Opened 21 years ago Closed 14 years ago

Browser (and email) stop working - claims to be "resolving host"

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: bpitman0001, Unassigned)

Details

(Whiteboard: bugday0420) 

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007

Similar to Bug 35031.  I searched through Google groups and have found similar
problems on multiple platforms, but none of them offered any suggestions for a fix.

Mozilla works fine for several hours, but then suddenly stops working.
Regardless of url, it claims to be "resolving host".  It hangs even when I use a
proxy server on 127.0.0.1.  Everything works fine again if I restart Mozilla.

I have several machines with Mozilla.  The one having problems is Windows 2000
Professional with Mozilla 1.5 (it also had problems with 1.0, 1.2, 1.3 and 1.4).

I have 3 RedHat 8.0 machines with Mozilla 1.1 and 1.2 and 1 Windows 2000 Pro
with Mozilla 1.4 that behave properly.  I use the Mozilla Email client on both
the Windows machines.

Reproducible: Didn't try

Steps to Reproduce:
I have no idea what causes the problem.  The machine effected "crashes" 1-2
times a day.
Actual Results:  
Mozilla stops working.  I can't check email or browse the web.

Expected Results:  
I think it should check my email and load web pages.

Default config except, Google selected and default page is blank.  I also use a
proxy on localhost (1 of the RedHat machines uses a localnetwork proxy)
exactly the same problem with my 1.5 and W98
Exactly the same bug. After some hours of work (or inactivity for that matter)
mozilla browser and mail stops working (meaning: will not load anyt content) and
claims 'resolving host .." in status bar. 

I Have not found a fix or a reason, but i can quarantee, that the url mozilla
tries to resolv is both perfectly resolvable and on-line.. 

OS: RedHat Linux 9 on X-Windows with the Gnome desktop. 
Have not tried with other window managers, but the bug is presistent and
repeating constantly.

Also, the bug was in 1.4, 1.4.1 and now in 1.5.

This bug seems to be slipping through the cracks.  I increased the severity in
hopes that a developer will look into it.
Severity: normal → major
Does this problem occur in recent builds in addition to the older ones (1.0,
1.4) you cited? If so, there's some things you can try. First, always make sure
to install Mozilla to an empty directory rather than on top of an old version,
since sometimes old incompatible files get left behind causing conflicts. Also,
you can try creating a new profile either by deleting your old one or running
the Profile Manager. Are you behind a proxy server, and if so, are the settings
in Mozilla the same as the ones in Internet Explorer (or whichever internet
programs you have installed that do work)? Just trying to eliminate some common
sources of problems.
OS: Windows 2000 → All
I've seen this on RH 9 and Mozilla 1.4 and Firebird 0.6 and 0.7
and WindowsXP and Firebird 0.6 and 0.7.
I created a new profile (default settings, no email).  Mozilla ran perfectly for
48 hours, then I restarted Mozilla (intentionally) and it has run ok for 24
hours.  It's enough to convince me that the problem is not present.

I'm going to try adding email to this new profile. (will not auto check on
start-up, no check every N minutes, no auto download, leave messages on the
server, no delete if deleted in Mozilla, no remember password - should only get
a copy of the new emails if I click on 'Get Messages' and I enter my password)
I am running RH9 athalon.  Mozilla 1.5 sea.  My bug crops up about every 6 hours
or so.  I have imap mail set up.  I use several tabs I store the sessions for. 
Sometimes it fails to resolve at get go.  All the tabs I use throught the day
work fine even when the bug crops up.  New tabs will not resolve requested urls.
 Going to newsgroups fail as well via the mail client.  Have serveral 1.5
clients running on W2K with no reports of this bug.  They mostly just use it for
email.
Added email to new profile and did not experience any problems (though, I didn't
really use the email client after setting it up and downloading email once).

The old profile still crashed after several hours of use.

Changed navigator preferences in new profile to open email only when mozilla is
started.  Still no problem.

Rebooted machine and tested old profile.  It's been several days now and the
problem hasn't resurfaced!!  :)

I'll add automatic email checking (and downloading) back into my oroginal
profile next week.
I have experienced this bug on Mozilla 1.5 on Red Hat 9.  It only manifests
itself when I have an IMAP email account setup. and in this case appears
regularly.  Deleting the email account causes the bug to cease.

My IMAP uses SSL on port 993;  don't know whether this is significant.

Update - the bug's back, and no IMAP in sight.  Sigh.  But the IMAP email
account seemed to increase the frequency of occurence (therefore deceiving me
into thinking I'd made it go away, sorry).

Laptop battery died, which forced a "reboot."  Shortly after starting mozilla,
email client asked for my password at a time that it had no business to ask.
(I've disabled all auto processes with email).  Less than 24 hours later, I
found Mozilla "frozen."  See also Bug #225637 (email prompting for password at
unexpected times).
One extra thing I've noticed is that sites with existing pages open [in other
tabs] continue to work, even though all new DNS names seem to get stuck
"resolving host".  For example, I usually have a Google tab or two on the go,
and even after DNS names stop resolving, I can successfully search from the
Google tabs.  Of course I can't hit any of the links in the search results :(

I've also noticed that Mozilla does not exit properly after having the
"resolving host" problem.  A mozilla-bin process keeps running even after all
windows are closed, which has to be killed manually.

Running Mozilla 1.5 on RH9.
As I've already said, I created a new profile with the same email setup as the
profile I have problems with.  I'm not sure how my old profile becomes unstable,
but the first indication that something is wrong has been with the email client
asking for my password at a time that it shouldn't even be checking email.  Once
corrupt, the profile will stop resolving within about 8 hours.  Restarting the
browser (and/or the computer) does not correct the problem.  However, loading
the new test profile and checking email at least once will fix the old profile!!
 Well, until it gets corrupted again (probably withing a few weeks).
Can confirm what Brent says. Creating a new profile with
all my SIMAP accounts, setting the new profile as default,
checking email once and then reverting to the old profile
fixes the problem for me.

RH9 and mozilla-1.5 with GTK-2.

Maybe this workaround should be put in the known issues
in the release notes until the bug is fixed?
I too have this problem, I'm running Mozilla 1.6 under FreeBSD 4.9 RELEASE-p1,
and  mozilla will suddenly stop loading pages, always claiming to be "resolving
host".

The workaround suggested in this thread did not work for me, however, I see a
pattern in mozilla's "freezes". It seems to quit on me whenever I'm visiting
sites that are heavy on advertising, especially if I have lots of tabs open (and
maybe a window or two). Try http://www.kvasir.no - enter something into the
search field and press the button. My mozilla hangs there every time. 

Maybe it's got something to do with certain tracker-cookies? I don't know, web
architecture isn't my strong point.

Either way, I placed a vote, because this is the single most annoying aspect of
using mozilla at present.

Henrik, I don't have a problem with http://www.kvasir.no/.  If what you're
experiencing is a Mozilla bug, I think it's a different one than this.
Brent:

If it's not this bug, then there's another with the exact same symptoms. I've
tried going at it methodically, trying different profiles, with IMAP accounts,
without IMAP accounts, revisiting sites which have produced the condition
previusly, etc... And the only consistency I've uncovered is the fact that
Kvasir and one other page, buried deep inside a website, induce the condition
every single time. All other webpages I've tried work sometimes, sometimes not.

Another peculiar thing is the whole deal with the mozilla process not dying when
I exit mozilla during its hangups. Up until about a week ago, I had to manually
kill the process, even after closing all the windows, composer, etc... As of
late, however, I no longer have to do this. This is weird, since I have not
rebuilt mozilla in a while (I'm running the latest cvsupped non-devel version).

I'll do some more testing, and see where it takes me.
Henrik, what you've described sounds quite different than the problem I had.  If
I left Mozilla running when I went to bed, it would be broken when I woke up
(every time!).  I always experienced an email oddity before Navigator stopped
working.  It had nothing to do with the # of windows/tabs open.

It's possible that you're experiencing a different path to the same "frozen"
state that is described in this bug.  If you want your problem to get the
attention it deserves, I'd file a seperate bug.  It's not going to be seen if
it's the 15th comment of this bug.  Bugzilla maintainers can always mark it a
duplicate of this one if necessary.




I've been seeing similar behaviour since 1.7RC1. IMAP email. Windows XP.
Everyone else has already provided ample description of the symtoms.
I also see this in Mozilla 1.7.2/Linux.  Not using mozilla email at all. 

When I go to the commandline and lookup the hostname with dig or nslookup, I get
a result instantly.
Product: Browser → Seamonkey
This is just an important bug, really really annoying. I am surprised it has not
even been looked yet, over a year.  Maybe it never will be and that is a shame...

Anyway, I found a workaround for this one, just by playing around:
When this starts happening, open a new tab, go Offline and try to go to a
location which would not be in  your cache(Then Mozilla will complain that it
cannot browse there when Offline). Go Online again. Off you go, your browser is
operational again.
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Anyone still seeing this bug? If you do, speak up, or it will be resolved WORKSFORME
Whiteboard: bugday0420 [CLOSEME WFM 2010-05-20 see comment #23]
No reply within a month, closing as WFM. Please note that I never was one of those who could see it, but there is no point in keeping a bug open for an issue reported against a version for which we dropped support. If you find that it still happens with SeaMonkey 2.0 or later, please open a new bug. Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Whiteboard: bugday0420 [CLOSEME WFM 2010-05-20 see comment #23] → bugday0420
You need to log in before you can comment on or make changes to this bug.