Closed Bug 775140 Opened 12 years ago Closed 12 years ago

Thunderbird hanging frequently

Categories

(Thunderbird :: Mail Window Front End, defect)

10 Branch
x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: csc4096, Unassigned)

Details

(Keywords: hang, Whiteboard: [addon:Lightning])

User Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.5) Gecko/20120606 Firefox/10.0.5
Build ID: 20120606062003

Steps to reproduce:

Thunderbird 10.0.6 x64 on RHEL6.3

Hangs frequently (up to 10 times a day) requiring process to be killed and restarted. No crash messages either in dmesg or /var/log/messages. Error console lists nothing out of the ordinary.


Actual results:

Folder name text disappears on the left-hand-side leaving only the icons visible.

Options in the top menu expand to show drop-down menu on clicking but none of the drop-down menu items are themselves clickable.

It looks very much like a gtk problem however no other program is exhibiting issues.

Running with NSPR_LOG_MODULES=ALL does not produce any crash information: log listing appears to stop well before the crashing process.


Expected results:

Thunderbird remaining stable and useable.
any change using safe mode http://support.mozillamessaging.com/en-US/kb/safe-mode ?

see https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report & attach stacktrace as a file to this bug
Severity: normal → critical
Keywords: hang
Thanks for that. The user in question is out of the office so it will probably be a few days before I can try those.

I do however have a few strace logs I ran on the machine a few days ago under Thunderbird 10.0.5 (it also crashed with similar effects). If those are of use then can you tell me how to upload them privately - they contain some company-sensitive information?
downgraded user to  thunderbird-lightning-1.2.1-1.fc16.x86_64.rpm and the crashes stopped.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Whiteboard: [addon:Lightning]
You need to log in before you can comment on or make changes to this bug.