76686 - Closing (exiting) mail/news - second time - hangs all of mozilla (with IMAP mailbox(es))

Status: RESOLVED FIXED

(MailNews Core :: Backend, defect)

Description

[Troy Telford]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.3 i686; en-US; rv:0.8.1+) Gecko/20010418
BuildID:    2001041809

I spent a good deal of time studying this; it happens in both Win32 and Linux.

I use IMAP for email; I have three accounts on two servers (one server has two
accounts).  Under the servers and settings options, all are set to auto-login,
empty trash on exit, and expunge inbox on exit.

The first time the mail window is opened/closed, everything works fine. 
However, if I open the mailbox a second time, do anything I normally do in
mail/news, and close the window again, and all of mozilla crashes, and a mozilla
process takes up 100% of the processor time.

Reproducible: Always
Steps to Reproduce:
1. Set mail/news as in Description.
2. Open Mail/News.
3. Close mail/news.
4. Open mail/news.
5. Close mail/news.

Actual Results:  Mozilla processes become unresponsive, utilize 100% processor time.

Expected Results:  Mail/news closes

Upon further investigation, I discovered the following:

* behavior is independant of number of email accounts.
* behavior is independant of autologin.
* behavior is independant of empty trash on exit.
* behavior is independant of which account has these settings (meaning all, two,
or just one account has these setting(s) ).

This leads me to believe these settings are not reponsible.

However, if any number of accounts is set to 'Clean up (expunge) Inbox on exit',
the mozilla will become unresponsive, and utilize 100% processor time;
effectively crashing Mozilla, which must be killed.  As mentioned before - it
does not matter how many mailboxes are set to expunge the inbox on exit -
whether one, two, or all three, in any combination.  Still crashes.

As I am unfamiliar with commands to log what happens, and more in-depth
bug-finding, any additional testing/logs that I can provide will be provided
should anybody give me suggestions/procedures on what to test further.

Comment 1

[Boris Zbarsky [:bzbarsky]]

duplicate of bug 76577?

Comment 2

[Gilles Durys]

*** Bug 76693 has been marked as a duplicate of this bug. ***

Comment 3

[Keyser Sose]

Possibly but we need more info...Reporter can you take a look at bug 76577 and
see if its the same? And/or even better give us the stack trace or talkback id
from the crashes your seeing? Thanks in advance.

Comment 4

[Troy Telford]

I've read bug 76577, and it appears to be very similar, if not the exact same.

Unfortunately, 76577 doesn't go into as great of detail as to what settings are
being used (IMAP/POP, expunge/purge, etc.)  Also, from what I read, the reporter
uses a different style of reading the mail than I do; it lists the problem as
closing multiple mail windows - which leads me to believe they are opening a new
message window for each email read?

Also, bug 76577 doesn't go into detail about the frequency;  in my experience, I
only use the 'main' mail/news window, so the multiple window closing may or may
not be a problem.  I'll test that.

But for me, if I do not have the IMAP settings to "Clean up (Expunge) INBOX on
exit", then Mail/News will close fine without error every time.

Either way - I'll get in some talkback ID's;

Comment 5

[Troy Telford]

I have at least been able to find this:

Problem #1 - I was referring to it as a crash; it's more like mozilla
hangs/freezes.  Mozilla becomes unresponsive and my process list displays the
mozilla process as consuming 99% of the processor time.

As long as the "Expunge inbox" is not set in the preferences, there are no
freezes, whether closing multiple windows as in bug 76577, or when just closing
a single mail window.  Mail/News can be closed and re-opened at will, without
any trouble.

However... getting a talkback report is a bit difficult.  Although talkback is
installed (and I have the talkback program running), when I set my system up to
hang mozilla (turned on "expunge inbox") when Mozilla hung, and the CPU usage
went to 100%.  The netscape quality feedback agent registered nothing.  The only
way to regain control was to kill the mozilla process from a command prompt
(linux) or Visual Studio's Process Viewer app.  (Ctrl-Alt-Delete is fussy in
'98, after all...)

I have run into this exact same behavior on both Win32 (on Win98 first edition),
and on Linux (Kernel 2.4.3).

In Linux, I clicked on its "Incidents... Generate Incident" in case it caught
anything.  It's TB29358935M.  So it has anything useful, go for it.  But it
wasn't the normal "mozilla crashed, incident is auto-generated and sent" deal,
so I doubt it did anything.

I am inexperienced with TalkBack, and am not sure how I am supposed to get a
stack trace as Mozilla does not crash- it hangs. So some specific instructions
(or where to look) will surely help me out.

Here is what is returned to stdout in Linux.  Notice mail loaded and
closed/cleaned up fine the first time.  It hung on the second time.

[troy@sl3xd /usr/local/mozilla]$ ./mozilla
./run-mozilla.sh ./mozilla-bin
MOZILLA_FIVE_HOME=/usr/local/mozilla
  LD_LIBRARY_PATH=/usr/local/mozilla:/home/troy/.kde/lib:/usr/lib
     LIBRARY_PATH=/usr/local/mozilla:/usr/local/mozilla/components
       SHLIB_PATH=/usr/local/mozilla
          LIBPATH=/usr/local/mozilla
       ADDON_PATH=/usr/local/mozilla
      MOZ_PROGRAM=./mozilla-bin
      MOZ_TOOLKIT=
        moz_debug=0
     moz_debugger=
 I am inside the initialize
 Hey : You are in QFA Startup
(QFA)Talkback loaded Ok.
Registering plugin 0 for: "*","All types",".*"
Document http://my.netscape.com/ loaded successfully
imap://[e-mail]/INBOX
imap://[e-mail]...skipping, already opened
An error occurred updating the cmd_copyLink command
An error occurred updating the cmd_copyImageLocation command
An error occurred updating the cmd_copyImageContents command
 
OnUnload from XUL
Clean up ...
imap://[e-mail]/INBOX
imap://[e-mail]...skipping, already opened
 
OnUnload from XUL
Clean up ...

Comment 6

[Asa Dotzler [:asa]]

talkback report does not contain a stacktrace.
http://cyclone/reports/incidenttemplate.cfm?bbid=TB29358935M

Comment 7

[Troy Telford]

I was afraid of that; actually thought that would happen.

I would guess this is mainly because the program doesn't crash - just keeps
running, using 99% processor time.

So how would I go about getting something useful to you if I can't get anything
useful from Talkback, or from the Win98 crash stack dump?

As I have this problem in both Windows and Linux, instructions for
either/or/both would be appreciated!

Lastly, this bug still exists on today's build - 2001042404 (win98)

Comment 8

[Keyser Sose]

The best thing is to download a nightly build with a talkback report and then
keep crashing it giving us 3 or 4 talkback ids (thus if one doesnt get through
some will). Then we can go from there. Thanks for your patience.

Comment 9

[Boris Zbarsky [:bzbarsky]]

ksosez, this is not a crash....  It's a hang.  Updating summary accordingly.

Troy, I can tell you how to get useful info on Linux....  Please read
http://mozilla.org/unix/debugging-faq.html -- pay particular attention to item
22.  Then you want to go to http://sources.redhat.com/gdb/, scroll down to
"Development version:" and grab the source from cygnus.com or one of the
mirrors.  You basically want a recent CVS source.  Any gdb that was checked out
of CVS before sometime this last winter is definitely no good.  So, grab the
sourc, build it, install it.  If you don't want to clobber your system's gdb
(and you probably don't) use --prefix=/home/${USER}/gdb for configure.

Once you've done that, make sure /home/${USER}/gdb/bin is in your PATH _before_
the dir where the system gdb is.

Now you should be all set.  Run 'mozilla -g', at the gdb prompt type 'run'.  Get
Mozilla to hang.  Hit Ctrl-c in the gdb window, and type 'bt' at the prompt you
get.  This will output a stack trace.  Copy this into a file, and attach it to
this bug as text/plain.  :)

Comment 10

[Troy Telford]

OK, I'll get the gdb stack trace sometime tomorrow.

And - one question:

You mention GDB for the Linux version - as I also have Visual Studio (win32) is
there anything I can do to get stack-traces there?

(I'm replying after reading the last post; I haven't done the RTFM bit just yet,
so if it's there, sorry in advance.)

Comment 11

[Boris Zbarsky [:bzbarsky]]

I'm pretty sure you can get stack traces with visual studio, but I don't know
how...

Comment 12

[Keyser Sose]

*** Bug 70129 has been marked as a duplicate of this bug. ***

Comment 13

[R.K.Aa.]

Reporter: Are you still seeing this bug?
Unable to reproduce on a current linux CVS build

Comment 14

[Reinout van Schouwen]

I'm observing this with 0.9.5 on my Mandrake 8.1 box. But I don't have to
open/close multiple times first; MailNews hangs *every time* when I try to close
it. This is pretty bad... :(

Comment 15

[lchiang]

http://bugzilla.mozilla.org/show_bug.cgi?id=97525 may be related.  I see three
bugs so far on hang on exit having to do with expunge.

http://bugzilla.mozilla.org/show_bug.cgi?id=97525
http://bugzilla.mozilla.org/show_bug.cgi?id=98328
and this bug.

Comment 16

[flacco002]

I'm seeing this bug (or something a lot like it).  Or, more accurately, one of
our users is seeing it after I told him how great Mozilla was  :-(

Mozilla locks up and processor goes to 100% in IMAPS mail.  The user did NOT
have "expunge" set, AFAIK.

This has been around for about a year - does anyone know what's up?

Comment 17

[flacco002]

I'm seeing this bug (or something a lot like it).  Or, more accurately, one of
our users is seeing it after I told him how great Mozilla was  :-(

Mozilla locks up and processor goes to 100% in IMAPS mail.  The user did NOT
have "expunge" set, AFAIK.

This has been around for about a year - does anyone know what's up?

Comment 18

[Dan Mosedale (:dmosedale, :dmose)]

Another way to get a stack trace on linux with somewhat less work is this: once
the application is hung, do "killall -SEGV mozilla-bin" from a shell.  This will
artificially cause a crash and trigger talkback to send in the stack.

Comment 19

[pedrum]

This continues to happen on 1.0 RC2 with Linux and IMAP. 

It only seems to happen when the "Empty Trash on Exit" option is selected.

For me, all of mozilla-bin hangs on the first close of the mail window when this
option is enabled. No dead processes, no 100% CPU util, the window refuses to
redraw and needs to killed.

Comment 20

[Russell Odom]

*** Bug 97525 has been marked as a duplicate of this bug. ***

Comment 21

[Russell Odom]

As per duplicate, OS -> all, nominating for 1.1. Also adding to summary to make
bug easier to find.

Just spent more than an hour doing some testing (Win2000, 1.1a): opening
mail/news, trying some combination of the following, then closing mail/news, and
seeing if this causes a browser window to become unresponsive. So far, I have
been unable to reproduce this at all.

I have tested it with (I think) all combinations of the following, with internet
connection up and Mozilla in on-line mode...
* Enabling/disabling 'Expunge in exit'
* Enabling/disabling 'Empty trash on exit'
* Whether or not I recieve any messages
* Whether or not I do a 'Compact folder' on inbox before exiting
* Whether or not I delete any messages before exiting

AFAIR, in all cases where I have got the hang to happen (my usual settings):
* Mozilla is in on-line mode
* 'Expunge on exit' is enabled
* 'Empty trash on exit' is enabled
* I have had Mozilla open for several hours at least (is this the key?!)

Still getting it when I'm *not* trying to reproduce it, though! I hate this bug!

Is there any way we can get a snapshot of what Mozilla is doing (on Windows)
when the hang is happening? Something we can do with Visual Studio? Some other tool?

Comment 22

[Russell Odom]

I just got this bug on 1.1b, so it's not gone away :-(
Can't figure out I did to trigger it still, except (as noted above) I'd had
Mozilla open for a while (a few days).

Symptoms: 0-1% CPU activity throughout. Attempted to close mail window with
browser window open - mail window didn't close, both open windows became
unresponsive. Eventually (after a minute or so - perhaps once mail cleanup had
finished, since there was still network activity?) the mail window closed, but
browser window remained unresponsive. Had to kill it with task manager.

Comment 23

[Carlos Rodrigues]

Just a "me too" kind of comment. I'm experiencing this with mozilla 1.6.

Comment 24

[Wayne Mery (:wsmwk)]

Is this problem gone for you?


(other bugs mentioned here, bug 97525 and bug 98328, are resolved)

Comment 25

[Troy Telford]

Seems to work for me now.  I think it can be closed.