Closed
Bug 535799
Opened 16 years ago
Closed 13 years ago
Slower Seamonkey shutdown after each hibernation
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: pgwhite4381, Unassigned)
Details
(Whiteboard: [Halloween2011Bug])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.6) Gecko/20091206 SeaMonkey/2.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.6) Gecko/20091206 SeaMonkey/2.0.1
In Windows 7, I usually terminate a session with the Hibernate key. The more I do this, without rebooting, the longer Seamonkey takes to shut down, up to 25 seconds. Rebooting clears the problem, temporarily. The shut-down time appears to increase linearly with the number of successive hibernates.
Reproducible: Always
Steps to Reproduce:
1.Windows 7
2.Hibernate, repeatedly
3.Check Seamonkey shut-down time.
Actual Results:
Seamonkey takes longer to shut down with each recovery from hibernate.
Expected Results:
Shutdown from Seamonkey should have remained almost instantaneous.
Severity: normal → major
Summary: slow seamonkey shutdown → Slower Seamonkey shutdown after each hibernation
Version: unspecified → Trunk
Not sure, between hibernations Seamonkey is closed and opened again, or not? In other words, to reproduce
1) Start Seamonkey
2) Shutdown Seamonkey, check taken time
3) Start Seamonkey again
4) Hibernate 10-20 times
5) Shutdown Seamonkey, check taken time and compare to time in step 2
OR
1) Start Seamonkey
2) Shutdown Seamonkey, check taken time
3) Start Seamonkey again
4) Hibernate
5) Wake up
6) Shutdown Seamonkey, check taken time
7) Start Seamonkey again
8) Repeat steps 4-7 10-20 times
9) After each Hibernate Seamonkey shutdown time grows on same amount of windows/tabs?
Also, are you using clean Hibernate ot Hybrid Sleep? What is memory usage while this test?
No reply on Comment 1 for almost 5 month, closing as incomplete
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•