Hemant Mohan Reporter
	Description • 15 years ago

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091016 Firefox/3.5.4
Build Identifier: 1.0 Pre (30-OCT-2009)

Tried to install Lightning extension on TB 3.0B4 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4pre) Gecko/20090915 Thunderbird/3.0b4).
I have tried a number nightly builds of Lightning during September - October 2009.
While starting Thunderbird, it hogs the CPU with CPU usage for TB going up to 60-70% on WinXP-SP3.  
Thunderbird fails to start even after 10 minutes, and the only way to resume work on the PC is to kill the Thunderbird process.  
Lightning could not be cleanly uninstalled as TB could not start up completely.  Thunderbird can start up, only after removing the Lightning related entries manually from extensions directory, extensions.rdf, extensions.cache, extensions.ini.

The problem was not observed with Thunderbird3 Beta 3.

Reproducible: Always

Steps to Reproduce:
1.Install Lightning 1.0Pre nightly on TB3.0 B4 on WinXP SP3
2.Try to start Thunderbird
3. Thunderbird fails to start even after waiting for 10 minutes and Windows Task Manager shows CPU hog by Thunderbird process.
Actual Results:  
Thunderbird fails to start up even after waiting for 10 minutes. Thunderbird hogs upto 60-70% CPU and memory usage is also around 300 MB

Expected Results:  
Thunderbird should normally start within a 5-10 seconds without hogging the CPU, and CPU usage should drop to 0-2 % under normal usage. Memory usage should also not grow above 50-60 MB.

	Philipp Kewisch [:Fallen] [:📆][:🧩]
	Comment 1 • 15 years ago

This may be fixed with bug 494140. Please try tomorrow's nightly build and let it sit through the whole process (may take a long time, sorry)

If you want the quicker solution and have a bit background knowledge, try executing the SQL in the patch to the mentioned bug. It is explained in a bit more detail in one of the later duplicates to that bug.

You can also just create a new profile, that should fix things, if bug 494140 was the culprit.

	Hemant Mohan Reporter
	Comment 2 • 15 years ago

I have applied the nightly build dated 08-Nov-2009.  It works fine now even with my old calendar data.
Thanks for the update.