Closed
Bug 80586
Opened 24 years ago
Closed 24 years ago
Raising moz after long period (30m) of inactivity causes very long wake-up time
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
People
(Reporter: pml, Assigned: asa)
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9) Gecko/20010505 BuildID: 2001050515 If I leave Moz sitting idle in the background of my desktop for a longish period (+/- 30 mins) and then raise it, it takes about 30 seconds to become responsive again. Mad disk activity before it becomes usable again. Reproducible: Always Steps to Reproduce: 1.Open moz, browse a little 2.Leave it in the background, dont touch it 3.Give it 30 mins to be safe 4.Raise it to interact again 5.disk grinding, lots of thinking - window outline is available, but contents empty until it wakes up completely Actual Results: browser responsiveness takes long enough to be irritating. Expected Results: idle window-rainding should be (almost) immediately responsive Is this perhaps just Win2K's dodgy VM system ? I would say yes since the OS should handle bringing apps back to life after the memory has been swapped off somewhere else, but all other apps under windows are basically immediately responsive after sitting idle for a long time. Is Moz's footprint to big to have state kept long enough ? Altho this is reported on 0.9, I have seen the same behaviour on nightly builds up until 20010505xx
Comment 1•24 years ago
|
||
*** This bug has been marked as a duplicate of 76831 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•