Closed Bug 448360 Opened 17 years ago Closed 16 years ago

SeaMonkey get lazy after a while

Categories

(SeaMonkey :: MailNews: Message Display, defect)

SeaMonkey 1.1 Branch
PowerPC
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: timd_huang, Unassigned)

Details

(Keywords: perf, Whiteboard: [needs test new profile] )

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.16) Gecko/20080703 SeaMonkey/1.1.11 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.16) Gecko/20080703 SeaMonkey/1.1.11 This problem started since 1.1.09 (?). After the SeaMonkey started for a while, perhaps, 15 or 30 minutes, opening a mail or visiting a new webpage got slower and slower with the spinning ball turning around and around. The only way I know to cure this is to quit and restart the SeaMonkey. Somewhere somehow, there must be a bug to cause this performance degradation. Please fix it asap. Reproducible: Always Steps to Reproduce: 1. Start the SeaMonkey (everything works fine so far) 2. Do something else for 15 or 30 minutes, and come back to SeaMonkey. 3. Try to surf a webpage or open a mail. Actual Results: SeaMonkey gets lazy after a while. Expected Results: Performance degraded to unbearable.
Just wondering: Can you create a second profile (see http://kb.mozillazine.org/Profile_Manager#Mac_OS_X) and see if it also gets slower and slower with the new profile?
I did not try the above with a new profile. It would take up too much of times on moving a few files a time and wait for 30 minutes or so to see if such a file caused the problem. However, when I checked the Mac System Monitor, I noticed the followings. I don't know if these help to see the cause of the problem. 2008-07-31 08:08:03.812 seamonkey-bin[555] WARNING: _wrapRunLoopWithAutoreleasePoolHandler got kCFRunLoopExit, but there are no autorelease pools in the stack. 2008-07-31 17:48:33.050 seamonkey-bin[983] WARNING: _wrapRunLoopWithAutoreleasePoolHandler got kCFRunLoopExit, but there are no autorelease pools in the stack.
I do not want you to move all files, I just want you to test with a plain new profile to see if it's possibly a problem within the profile.
(In reply to comment #3) > I do not want you to move all files, I just want you to test with a plain new > profile to see if it's possibly a problem within the profile. > OK, I'll try that. But, remember, this delay won't take place after I run the SeaMonkey for at least 15 - 30 minutes.
QA Contact: search
Version: unspecified → SeaMonkey 1.1 Branch
Timothy, what results do you have with new profile using latest v1.1.x? high cpu? if it fails with newest, then test with trunk build would be even better, in a new profile http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/
Keywords: perf
Whiteboard: [needs test new profile] closeme 2009-06-05
Assignee: mail → nobody
QA Contact: search → message-display
=> incomplete due to no response please reopen if you can reproduce with newer build like http://www.seamonkey-project.org/releases/seamonkey2.0b1/
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [needs test new profile] closeme 2009-06-05 → [needs test new profile]
You need to log in before you can comment on or make changes to this bug.