Mail got slow down after running SeaMonkey for several minutes

RESOLVED INCOMPLETE

Status

--
major
RESOLVED INCOMPLETE
11 years ago
8 years ago

People

(Reporter: timd_huang, Unassigned)

Tracking

({perf})

SeaMonkey 1.1 Branch
PowerPC
Mac OS X

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9

I'm running the "stable" version of SeaMonkey. However, I encountered this annoying problem since the last and current "stable" version.

The problem is like this:
When I start the SeaMonkey and open the mail. Everything works OK. Clicking to another letter will show up immediately. Nothing wrong here.

However, if I work outside SeaMonkey for say 5 or 10 minutes and back to it, the mail openning will be so slowed down with "loading message...". It may take minutes to load a previously opened letter. This situation gets worser and worser, till I'm forced to quit SeaMoney and restart it. Then, everything works fine.

This is a serious problem. I hope it can be thoroughly investigated and solved.

Reproducible: Always

Steps to Reproduce:
1. Open SeaMonkey, go to Mail
2. Open any mail. Then, go to desktop and do something else for several minutes
3. Back to SeaMonkey Mail. "loading message ..." will show up with spinning ball
Actual Results:  
Mail got slowed down so much to unbearable. Forced to quit and restart SeaMonkey.

Expected Results:  
Not slowed down after opening up SeaMonkey for several minutes. Please fix the problem.
(Reporter)

Comment 1

11 years ago
Please, please, fix this problem as soon as possible.

The slowing down problem is getting worse, and getting my limit. 

I'm using a stable version. It should NOT have this kind of problem.
Severity: critical → blocker
(Reporter)

Updated

11 years ago
Version: unspecified → SeaMonkey 1.1 Branch
(In reply to comment #0)
> I'm running the "stable" version of SeaMonkey. However, I encountered this
> annoying problem since the last and current "stable" version.

Was is working fine with a previous release ?
What regression timeframe would that be ?

> However, if I work outside SeaMonkey for say 5 or 10 minutes and back to it,

Does it happen too if you work _inside_ SeaMonkey for that long ?

> minutes to load a previously opened letter. This situation gets worser and
> worser, till I'm forced to quit SeaMoney and restart it. Then, everything 

Are you noticing any abnormal CPU/memory usage ?
Severity: blocker → critical
(Reporter)

Comment 3

10 years ago
I'm using 1.1.9 now. Similar situation since 1.1.8.

As long as "inside" SeaMonkey, it seems OK.

I'm using G5 iMac mainly.

Comment 4

10 years ago
sounds network related.  Are you wireless, broadband or dialup?
*from comment 2) Is CPU or memory usage high or low?

please retest the release prior to 1.1.8 and confirm the problem does not happen there.
(Reporter)

Comment 5

10 years ago
I'm using 1.1.9 and did not keep older version. Sorry.
(Reporter)

Comment 6

10 years ago
By the way, CPU and memory were not the cause of the problem.

Comment 7

10 years ago
(In reply to comment #6)
> By the way, CPU and memory were not the cause of the problem.

The question about CPU... is relevant please - symptoms can be helpful clues to determining what IS the problem.


(In reply to comment #5)
> I'm using 1.1.9 and did not keep older version. Sorry.

you can get an older release from ftp://ftp.mozilla.org/pub/seamonkey/releases/

Comment 8

10 years ago
alpha 2 is available at http://www.seamonkey-project.org/releases/2.0a2

do you see this problem with alpha 2?
Severity: critical → major
Keywords: perf
Whiteboard: closeme 2009-02-01

Comment 9

9 years ago
no response :(
=> incomplete
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE

Updated

8 years ago
Whiteboard: closeme 2009-02-01
You need to log in before you can comment on or make changes to this bug.