Closed Bug 191774 Opened 22 years ago Closed 22 years ago

Slow after inactive

Categories

(Core :: Disability Access APIs, defect)

x86
Windows 2000
defect
Not set
trivial

Tracking

()

RESOLVED DUPLICATE of bug 76831

People

(Reporter: magnolima, Assigned: aaronlev)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212 Even I am using version 1.3a now, I have noted that if the browser is not touched for a while it becomes more and more slow... I cant see this problem with my M13a at home, just here where I work. I tested leaving only the browser with any page loaded and after some minutes, it gets a long time when beginning to respond again. At home I use XP Pro and here W2K running a IBM Netvista 1Ghz. Reproducible: Always Steps to Reproduce: 1. leaving the browser alone for a while 2. 3. Actual Results: When I click on it to use again, i gets incrible slow. I doenst happens with any other application here, incluinding some development tools that I use. Expected Results: I really dont know if its a Mozilla problem :(
Is this related to bug 76831? Magno Lima, do you mean that Mozilla is very slow at the beginning (after you let it alone quite some time), but is normally fast later, after you worked with it for a while? Does this only happen when you minimized the Mozilla window? How much RAM do the two computers have? Anything special about the pagefile settings?
What about bios configuration for energy conservation ? - suspend to disk - switch off disk after x mins of inactivity - what events are needed for staying alive / wake up? How long does it take that mozilla comes to speed again? 2 seconds, 20 seconds? Is it also slow if you try to open a local file?
it's a dupe of bug 76831 *** This bug has been marked as a duplicate of 76831 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.