400189 - Thunderbird spends >90% proc. cycles in thread jpeg_fcdt_islow+0x888a

Status: RESOLVED INCOMPLETE

(Core :: Graphics: ImageLib, defect)

Description

[RealMink]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7
Build Identifier: Version 2.0.0.6 (20070728)

Thunderbird spends more than 90% proc. cycles in thread jpeg_fcdt_islow+0x888a
It does this in any action like changing to a different mailfolder, getting new mail, doing some search on contents, opening an email ....; it certainly happens in actions that have nothing to do with pictures. It is so slow since at least the last 7 or 8 releases (>1.5 )

Reproducible: Always

Steps to Reproduce:
1.I just need to start THUNDERBIRD.
2.
3.



Theme out of the box.
Processor: x86 Family 6 Model 9 Stepping 5 GenuineIntel 1300 Mhz
Memory: 1GB
OS: WinXP Prof SP2 and all patches
Stacktrace shows CPU >90% in Thunderbird.exe!jpeg_fcdt_islow+0x888a

Comment 1

[Wolf [:wolf]]

Try a nightly build from the trunk and see if the problem still exists for you.
http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-trunk/thunderbird-3.0a1pre.en-US.win32.installer.exe

Some people have reported on mozillazine similar issues with Firefox, (1.5)
http://forums.mozillazine.org/viewtopic.php?t=406320&

jpeg_fdct_islow is the JPEG forward discrete cosine transform. Part of libjpeg.
http://mxr.mozilla.org/seamonkey/search?string=jpeg_fdct_islow

Comment 2

[Wayne Mery (:wsmwk)]

need to narrow this issue and a good testcase message would be useful - the more extreme the better.

Comment 3

[Wayne Mery (:wsmwk)]

RealMink, can you try an early release? http://www.mozillamessaging.com/en-US/thunderbird/early_releases/

bug 392394 comment 16 indicates the thread information may not be enough:  "We always decode on the main thread, so seeing jpeg_fdct_islow show up on another thread generally means that the symbol data is missing for that thread and it's picking up just the closest symbol.  Getting a stack for the thread that's consuming the CPU may be useful."

Comment 4

[Tyler Downer [He/Him]]

@Reporter, we have not heard back from you in a while, so I am closing this bug as INCOMPLETE. You can reopen this bug if more information becomes available.