602486 - Thunderbird 3.1.4 becomes unresponsive when running firefox 3.6.10

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

[Dan]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10
Build Identifier: 3.1.4


Latest Thunderbird frequently becomes  "unresposive" ie hangs up when both Thunderbird and Firefox are running.  This after cleaning cache files and running other diagnostics, repairing permissions etc

Reproducible: Sometimes

Steps to Reproduce:
1. open thunderbird 3,1,4 in Mac OS X Tiger 10.4.1
2.open Firefox 3.6.1
3. begin working in both environments toggling back and forth
Actual Results:  
periodic not responsive prompts that sometimes requires force quitting of both applications

only occurs when both thunderbird and firefox running same time

Expected Results:  
force quitting resolves problem

Very annoying to have to start and stop both applications  and/or only run the applications one at a time.

Comment 1

[Wayne Mery (:wsmwk)]

Dan, 
Does this happen when you have many tabs open, or use lots of pages that are heavy in javascript, or after a week or two of being open?
What add-on extensions are installed?
Do you observe that CPU usage is high for either Firefox or Mac?

Comment 2

[Wayne Mery (:wsmwk)]

Dan,
additionally
- what type of disk drive are the profiles stored on?
- do you see this problem if you create and start in a NEW profile?  (do not delete the old profile)  see http://support.mozillamessaging.com/en-US/kb/Profiles
- what antivirus, and does situation improve if you turn off antivirus?  yes, close your network connection, and turn off AV?

(bizarre similarity to http://getsatisfaction.com/mozilla_messaging/topics/reordering_message_filter_is_slow?utm_content=reply_link&utm_medium=email&utm_source=reply_notification# which mentions firefox 3.6.10)

Comment 3

[Joshua Cranmer [:jcranmer]]

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.