298643 - 1.1a1 hangs for this IMAP user.

Status: RESOLVED WORKSFORME

(Thunderbird :: General, defect)

Description

[Matthew Elvey]

1.1a1 has hung a few times.  (I selected Trunk as the closest cousin.)  It's
completely unresponsive for over 20 minutes.  Cursor spins over menubar.  If I
force-quit, the crash reporter doesn't come up.

I got my build from
ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/1.1a1/mac/en-US/ and the
checksum was correct.

FYI:
% netstat | grep imap
tcp4       0      0  192.168.2.98.55376     gdc.groupd.com.imap    ESTABLISHED
tcp4       0      0  192.168.2.98.55375     gdc.groupd.com.imap    ESTABLISHED
tcp4       0      0  192.168.2.98.55374     gdc.groupd.com.imap    ESTABLISHED
tcp4       0      0  192.168.2.98.55363     office.nextbus.c.imap  ESTABLISHED
tcp4       0      0  192.168.2.98.55362     office.nextbus.c.imap  ESTABLISHED
tcp4       0      0  192.168.2.98.55358     office.nextbus.c.imap  ESTABLISHED
tcp4       0      0  192.168.2.98.55356     mail.messagingen.imaps ESTABLISHED
tcp4       0      0  192.168.2.98.55353     mail.messagingen.imaps ESTABLISHED
tcp4       0      0  192.168.2.98.55350     mail.messagingen.imaps ESTABLISHED

I mentioned this in passing in the Bug 206408 here:
https://bugzilla.mozilla.org/show_bug.cgi?id=206408#c95 

Sorry, not much detail to report, other than 1.0.2 continues to work quite
reliably.  I want the fix to the above bug, which seems to be in 1.1a1.

I could swear there was a way to enable error logging with a preferences setting
(i.e. an edit to prefs.js or user.js).  Isn't there? Or is
http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap really what
I need to do?

Comment 1

[David :Bienvenu]

yes, you want the protocol logging described by the document you linked to.
Though if Thunderbird itself is hung, it's not likely it's imap that's hung,
since IMAP runs on its own thread. So when it's hung, you can't open new
windows, etc?

Comment 2

[Matthew Elvey]

I'd been trying to get debugging working.  My result: the only unixish method
worked for me on OSX 10.4.

Dragging a text file with 
ARGS:-mail
ENV:NSPR_LOG_MODULES=IMAP:5
ENV:NSPR_LOG_FILE=/tmp/ThunderbirdDebugMode

in it onto my Tbird folder didn't enable logging, or result in a new file inside
the .app's MacOS folder.

This suggests the following edits:


Index: mozilla-org/html/quality/mailnews/mail-troubleshoot.html
===================================================================
RCS file: /cvsroot/mozilla-org/html/quality/mailnews/mail-troubleshoot.html,v
retrieving revision 1.18
diff -u -r1.18 mail-troubleshoot.html
--- mozilla-org/html/quality/mailnews/mail-troubleshoot.html	11 Nov 2004
14:29:03 -0000	1.18
+++ mozilla-org/html/quality/mailnews/mail-troubleshoot.html	12 Aug 2005
00:25:09 -0000
@@ -112,6 +112,16 @@
  <li>Expand the 'MacOS' tree, and your file should be right there.</li>
 </ol>
 
+<p>The above doesn't work for me, but this shell script does:</p>
+
+<pre>#!/bin/sh
+export NSPR_LOG_MODULES=IMAP:5
+#Normal users can't write to /var/log.
+export NSPR_LOG_FILE=/tmp/ThunderbirdDebugMode
+open "/Applications/Thunderbird 1.1+NightlyJul12.app/"
+
+</pre>
+
 <h3>Unix:</h3>
 <p>run the following commands before running mozilla, or add them to 
 the proper rc file (like ~/.cshrc for csh)</p>
@@ -119,7 +129,7 @@
 setenv NSPR_LOG_MODULES <a href="#protocol">protocol</a>:<a href="#level">5</a>
 setenv NSPR_LOG_FILE <em>/tmp/</em><a href="#filename"><em>filename</em></a>
 
-#(for bsh):
+#(for bash):
 export NSPR_LOG_MODULES=<a href="#protocol">protocol</a>:<a href="#level">5</a>
 export NSPR_LOG_FILE=<em>/tmp/</em><a href="#filename"><em>filename</em></a></pre>


Can someone confirm/deny that this edit is appropriate/the extant instructions
work on OS X?

I should have a log from my next crash within a few days. :) :( 

Comment 3

[Wayne Mery (:wsmwk)]

does this still happen with TB 1.5.0.4?
If so, please supply protocol log

Comment 4

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

(In reply to comment #3)
> does this still happen with TB 1.5.0.4?
> If so, please supply protocol log

Lack of information since last comment, WFM on Mac IMAP as well, 1.5.0.x is no longer supported.

-> WFM.