Closed
Bug 276021
Opened 20 years ago
Closed 19 years ago
after long idle being minimized pages will not load gives page cannot be found error
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: auxxx, Assigned: darin.moz)
References
()
Details
(Keywords: qawanted)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 After a long idle being minimized pages will not load. For example after a long wait I bring Mozilla back up, everything works, any pages that are open I can look at but not refresh. If I try to goto http://google.com.au it just sits loading, if I wait long enough it will say that this page cannot be found. To fix this problem I have to restart Mozilla. After this http://google.com.au loads in a few micro seconds. Reproducible: Sometimes Steps to Reproduce: 1. Open mozilla with any webpage. 2. Minimize and leave idle for a few hours. 3. Open it again and try to load any website, eg http://google.com Actual Results: Sat loading until the error message "http://google.com cannot be found" showed. Expected Results: Load Google right away.
Comment 1•20 years ago
|
||
I often leave Mozilla working for hours and didn't get any problems. I see that you are using Mozilla 1.7.3 Please download Mozilla 1.7.5 from http://www.mozilla.org/releases/#1.7.5 or the most recent nightly build from: http://www.mozilla.org/releases/nightly.html And check if you still see this problem then.
Okay I just downloaded and installed 1.7.5 last night. I left Mozilla minimized overnight and in the morning I was unable to load any website again. I couldn't even connect to my mail server via Mail & Newsgroups. I had to restart to get it working again. So maybe try leaving it overnight instead of a few hours. By the way, I havn't check this yet but I think I can access cached/local pages just fine. My home page always works, which happens to be located on C:. Its only pages that have to be reloaded or loaded from a non-local source that do not work.
Try going into start, control panel, administrative tools, services and select DNS client and then either right click and restart or click on the restart icon.
Updated•20 years ago
|
Version: unspecified → 1.7 Branch
Comment 4•20 years ago
|
||
auxxx: does Ian's suggestion help? ==> networking
Assignee: jag → darin
Component: XP Apps → Networking
Product: Mozilla Application Suite → Core
QA Contact: pawyskoczka → benc
No that didn't seem to help. Although I havn't had the problem for awhile becuase I started turning my computer off instead of leaving it on 24/7. But I think the problem is something to do with the way mozilla handles memory. It seems to leak memory a bit.
Comment 6•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 7•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•