Closed
Bug 227654
Opened 21 years ago
Closed 21 years ago
Serious slow down when a Windows XP machine wake up from hibernation, sleeping etc.
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
People
(Reporter: jongampark, Unassigned)
Details
(Whiteboard: DUPME)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007
When a machine with the Windows XP home edition ( but I think it will be true
with Professional version also. ), mozilla makes system slow and mozilla itself
slows down.
From drawing Mozilla's own window, pulldown menu bar to window/task switching,
the mozilla causes slow speed of operation.
Reproducible: Always
Steps to Reproduce:
1. Open mozilla browser, and surf some web sites
2. Make your system goes into hibernation or sleep.
3. After some time, wake up your machine.
4. Try to use your Mozilla browser.
Actual Results:
Slow speed in
- drawing mozilla window
- pull down menu
- selecting menu item
- window switching
- task switching ( even to other programs. )
Expected Results:
- It should not affect the performance, or at least if all resource required
is loaded, there should be no performance degradation.
Windows XP Home Edition
ThinkPad R32
RAM : 512MB
Free HDD space : more than 4GB
Comment 2•21 years ago
|
||
*** This bug has been marked as a duplicate of 76831 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPE → DUPME
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 3•20 years ago
|
||
This is not the same as #76831. It is the same as #206341 (which was also marked
as a duplicate of #76831). It has nothing to do with 'idle', but with time spent
in XP's 'stand by' or 'hibernate' modes, and there is no significant disk
activity during the long sluggish period. It is probably linked to Flash content
in open tabs. See my more detailed comments at #206341:
https://bugzilla.mozilla.org/show_bug.cgi?id=206341
You need to log in
before you can comment on or make changes to this bug.
Description
•