Front end seems to crash and be restarted at regular interval

RESOLVED INCOMPLETE

Status

Thunderbird
Mail Window Front End
--
critical
RESOLVED INCOMPLETE
7 years ago
7 years ago

People

(Reporter: David TYLSKI, Unassigned)

Tracking

({stackwanted})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [closeme 2011-02-11])

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 ( .NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2

When started, and around once a minute, Thunderbird takes 100% of one CPU (i.e. 50% on my double-CPU). Clicking on a 3-kB mail takes a lot of time to be loaded.

All the applications are impacted, frozen during about 10 seconds.

I suppose the interface crashes and restarts, since if I open a window to write a new mail and wait for the "crash", finally in the Windows XP taskbar is the main window displayed _on_the_right_side_ of the new writing mail (whereas before, it was on the left side, following the window creation order).


Reproducible: Always

Steps to Reproduce:
Occurs permanently.

Actual Results:  
Already described.

Expected Results:  
The interface shall be stable, not be restarted every minute.

It takes up to 90 seconds to display the main window.
RAM used: around 120 MB
When exiting, after disappearing from the taskbar, still runs, now consuming 90 MB during 30 seconds, before showing off from the Widnows task manager.

Global indexing activated
Cookies activated (currently 8 cookies stored only)
50 MiB cache, compacted if > 100 kiB gain

Automatic update lookup for Thunderbird + installed modules
Asking for what to do in case of update available

No security module activated
Antivirus on incoming mail (before storage): disabled

Installed (and active) modules:
AdBlock Plus 1.2.2
ConfigDate 0.7
Extra Folder Columns 1.1
File Bug Report 0.4
FoxClocks 2.6.18
Lightning 1.0b2
LightningButton 1.4
Noia 2.0 eXtreme XT 3.25
United States English Dictionary 4.0.0

Disabling Noia eXtreme does not change anything.

Comment 1

7 years ago
Are you seeing the crash reporter? https://support.mozillamessaging.com/en-US/kb/Mozilla+Crash+Reporter  If you are, please post your crash report.

Also, can you reproduce when started in safe mode?
 https://support.mozillamessaging.com/en-US/kb/Safe+Mode
(Reporter)

Comment 2

7 years ago
There was no crash report. Interface was restarted by itself (at least it appears to).
The list of actions was not different from what I successfully did (moving small mails for example).

This morning I did not duplicate the issue (that occurred however during days) in the normal mode; thus I did not try the safe mode. It is quiet and running fine.

The "ImapMail" folder takes 220 MB. I suspect the interface falling into some watchdog due to the cache processing, or something like that, the operation not being in background at all.

I keep monitoring the status of Thunderbird, in case of the issue occurring again, by keeping a "New mail" window open (its location in taskbar shall stay on the right of the one of main window - that was the point making me supposing that the interface was restarted).

Hope I may afford more information...

Comment 3

7 years ago
https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg
Keywords: stackwanted

Comment 4

7 years ago
do you still crash?

(In reply to comment #2)
> There was no crash report. Interface was restarted by itself (at least it
> appears to).

I would think it restarted because you submitted a crash report and the reporter restarted thunderbird.

Can you find the crash ID? http://support.mozillamessaging.com/en-US/kb/Mozilla+Crash+Reporter#Viewing_crash_reports
Whiteboard: [closeme 2011-02-11]
RESOLVED INCOMPLETE due to lack of response to previous question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.