Closed Bug 326160 Opened 19 years ago Closed 18 years ago

Extremely slow mail reading

Categories

(SeaMonkey :: MailNews: Message Display, defect)

SeaMonkey 1.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: carlos_vives, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.7.12) Gecko/20050915 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.7.12) Gecko/20050915 Every time I try to open a mail from any of my accounts, cpu goes up to 100% until Seamonkey Mail displays it on screen. That may take from 15 to 30 seconds for any mail, doesn't matter where it is or what it contains. Once opened, everything is fine, thought. When opening another mail, same happens. Tried Seamonkey 1.0b and 1.0 final. Using Mozilla Suite, now both installed on my system. Reproducible: Always Steps to Reproduce: 1. Open mail component 2. Clic on an e-mail
Related to/duplicate of bug 327552?
Evrything about that is true, on LINUX + pentium4 machines. Very slow reading the mail database ( 3 to 4 seconds !) versus 1/10 of second on Mozilla-1.7.12 .... In compatible with normal use. If not rapidly fixed .. need to go back to Mozilla-1.7.13 It looks like a really bug as CPU is 100% for showing a 3 lines mail !! LINUX LINUX
Evrything about that is true, on LINUX + pentium4 machines. Very slow reading the mail database ( 3 to 4 seconds !) versus 1/10 of second on Mozilla-1.7.12 .... In compatible with normal use. If not rapidly fixed .. need to go back to Mozilla-1.7.13 It looks like a really bug as CPU is 100% for showing a 3 lines mail !! LINUX LINUX
Now using: SeaMonkey 1.1.3 Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.8.1.5) Gecko/20070716 SeaMonkey/1.1.3 Mnenhy/0.7.5.0 but it seems to be fixed a few subversions ago (both win and linux), not sure which one.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Version: unspecified → SeaMonkey 1.0 Branch
You need to log in before you can comment on or make changes to this bug.