spin while replying to email with large attachments

RESOLVED EXPIRED

Status

MailNews Core
Composition
--
critical
RESOLVED EXPIRED
14 years ago
10 years ago

People

(Reporter: cesium, Assigned: (not reading, please use seth@sspitzer.org instead))

Tracking

({hang})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803

I received an email message with relatively large attachments.  (There were two
attached files:
[csimmons mozilla]$ wc /tmp/times?.txt
 100004  200000 2020259 /tmp/times3.txt
  33163   66325  861317 /tmp/times4.txt
 133167  266325 2881576 total
These files contain two colums of floating point numbers.  e.g.:
4.964650        12.045207
4.040510        5.265716
6.210560        9.687181
4.443060        6.588364

I clicked on the main email line to view the email, and then hit "reply" while
the main thread was still busy, presumably downloading the attachments from our
server.  (We use an IMAP server, probably with an Oracle database backend, so it
doesn't have hugely fast response time.)

After a few seconds of typing in my reply, the mozilla.bin process started
chewing up all available cpu.  After a few seconds, I kill the process.  This
happened in version 1.2.1, and I upgraded to version 1.7.2 in an attempt to
avoid this type of problem.

I attached to the process while it was spinning and took a stack trace.

Thread 4 (Thread 1091271872 (LWP 16417)):
#0  0xffffe002 in ?? ()
#1  0x400c3ed9 in PR_OpenDir () from /usr/local/mozilla/libnspr4.so
#2  0x4081a592 in NSGetModule () from /usr/local/mozilla/components/libnecko.so
#3  0x4081abd9 in NSGetModule () from /usr/local/mozilla/components/libnecko.so
#4  0x406e617b in nsThread::Main(void*) () from /usr/local/mozilla/libxpcom.so
#5  0x400c5579 in PR_Select () from /usr/local/mozilla/libnspr4.so
#6  0x400e72b6 in start_thread () from /lib/tls/libpthread.so.0
  
Thread 3 (Thread 1116941376 (LWP 16418)):
#0  0xffffe002 in ?? ()
  
Thread 2 (Thread 1160260032 (LWP 16424)):
#0  0xffffe002 in ?? ()
  
Thread 1 (Thread 1077627776 (LWP 16415)):
#0  0x41185cc7 in NSGetModule ()
   from /usr/local/mozilla/components/libgklayout.so
#1  0x4118c18e in NSGetModule ()
   from /usr/local/mozilla/components/libgklayout.so
#2  0x411dd0c2 in NSGetModule ()
   from /usr/local/mozilla/components/libgklayout.so
#3  0x41227b58 in NSGetModule ()
   from /usr/local/mozilla/components/libgklayout.so
#4  0x411d37a2 in NSGetModule ()
   from /usr/local/mozilla/components/libgklayout.so
#5  0x412e5709 in NSGetModule ()
   from /usr/local/mozilla/components/libgklayout.so
#6  0x41305f07 in NSGetModule ()
   from /usr/local/mozilla/components/libgklayout.so
#7  0x413046d8 in NSGetModule ()
   from /usr/local/mozilla/components/libgklayout.so
#8  0x4133bfb6 in NSGetModule ()
   from /usr/local/mozilla/components/libgklayout.so
#9  0x41f826b6 in NSGetModule ()
   from /usr/local/mozilla/components/libeditor.so
#10 0x41f967db in NSGetModule ()
   from /usr/local/mozilla/components/libeditor.so
#11 0x41c5753e in NSGetModule () from /usr/local/mozilla/components/libtxmgr.so
#12 0x41c59f5b in NSGetModule () from /usr/local/mozilla/components/libtxmgr.so
#13 0x41c58a99 in NSGetModule () from /usr/local/mozilla/components/libtxmgr.so
#14 0x41f7d2fc in NSGetModule ()
   from /usr/local/mozilla/components/libeditor.so
#15 0x41f7ebec in NSGetModule ()
   from /usr/local/mozilla/components/libeditor.so
#16 0x41f05840 in NSGetModule ()
   from /usr/local/mozilla/components/libeditor.so
#17 0x41f05c40 in NSGetModule ()
   from /usr/local/mozilla/components/libeditor.so
#18 0x41f76475 in NSGetModule ()
   from /usr/local/mozilla/components/libeditor.so
#19 0x41f22ffd in NSGetModule ()
   from /usr/local/mozilla/components/libeditor.so
#20 0x41f22dc0 in NSGetModule ()
   from /usr/local/mozilla/components/libeditor.so
#21 0x41f11869 in NSGetModule ()
   from /usr/local/mozilla/components/libeditor.so
#22 0x41ef8356 in NSGetModule ()
   from /usr/local/mozilla/components/libeditor.so
#23 0x44976f33 in NSGetModule ()
   from /usr/local/mozilla/components/libmsgcompose.so
#24 0x4497e283 in NSGetModule ()
   from /usr/local/mozilla/components/libmsgcompose.so
#25 0x41e99333 in NSGetModule () from /usr/local/mozilla/components/libmime.so
#26 0x44a02383 in NSGetModule ()
   from /usr/local/mozilla/components/libmsgimap.so
#27 0x408033e3 in NSGetModule () from /usr/local/mozilla/components/libnecko.so
#28 0x4080311d in NSGetModule () from /usr/local/mozilla/components/libnecko.so
#29 0x406cba41 in nsInputStreamReadyEvent::EventHandler(PLEvent*) ()
   from /usr/local/mozilla/libxpcom.so
#30 0x406e2b67 in PL_HandleEvent () from /usr/local/mozilla/libxpcom.so
#31 0x406e2a94 in PL_ProcessPendingEvents ()
   from /usr/local/mozilla/libxpcom.so
#32 0x406e477b in nsEventQueueImpl::ProcessPendingEvents() ()
   from /usr/local/mozilla/libxpcom.so
#33 0x41884665 in NSGetModule ()
   from /usr/local/mozilla/components/libwidget_gtk.so
#34 0x4188421d in NSGetModule ()
   from /usr/local/mozilla/components/libwidget_gtk.so
#35 0x402870a6 in g_io_add_watch () from /usr/lib/libglib-1.2.so.0
#36 0x402889ae in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#37 0x40288e89 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#38 0x40289124 in g_main_run () from /usr/lib/libglib-1.2.so.0
#39 0x4019427f in gtk_main () from /usr/lib/libgtk-1.2.so.0
#40 0x41884976 in NSGetModule ()
   from /usr/local/mozilla/components/libwidget_gtk.so
#41 0x41869884 in _Unwind_Find_FDE ()
   from /usr/local/mozilla/components/libnsappshell.so
#42 0x08056e0d in getCountry(nsAString const&, nsAString&) ()
#43 0x08057980 in main ()
#44 0x42015574 in __libc_start_main () from /lib/tls/libc.so.6

Reproducible: Sometimes
Steps to Reproduce:
1. Start replying to an email with large attachments while the attachments are
still being downloaded.
2.
3.
Actual Results:  
Cpu spin for multiple seconds.  (single processor box was 98% busy for multiple
seconds)

Expected Results:  
Not chewed up the cpu for multiple seconds with no sign of stopping.

Comment 1

14 years ago
has Mozilla crashed with 1.7.2? (submit a talkback report if it does)  Otherwise
this bug should be closed.
Keywords: crash

Comment 2

14 years ago
xref bug 161775.
(Reporter)

Comment 3

14 years ago
Andrew -- So, you're saying that serious performance problems which make the 
program unusable aren't a bug?  There was no crash.  As I stated, I aborted 
the program via "kill" after multiple seconds (more than 2) of non-
responsiveness and 100% cpu consumption.

Mike -- Did you type in the wrong number, or would you be interested in 
explaining how bug 161775 is related?



Comment 4

14 years ago
Sorry, I guess that was a little cryptic.

That bug is about attachments, displayed inline, being included in the quoted 
text of a reply.  In the case of IMAP, in order to include them, it seems the 
attachments are re-downloaded from the server before being quoted; large ones 
will introduce a sizeable delay.

I noted the similarity between this bug's report and bug 161755 comment 8.

One way to test whether this is the same problem: with a message that exhibits 
the problem, turn off  View|Display Attachments Inline  and then reply, see if 
it goes faster.
(Reporter)

Comment 5

14 years ago
Mike --  That makes sense.  By the by, I wasn't concerned with the time to 
download the attachment from the server as that seemed to progress just fine 
in the background without chewing up the cpu.  Once the download was done, 
however, it appears that two threads trashed each other and one went crazy and 
ate all the cpu.  If I carefully waited until the download is complete before 
typing in a reply, the problem didn't occur.  I don't remember the attachments 
being displayed inline on either the original or the response.

Updated

14 years ago
Keywords: crash → hang
Product: MailNews → Core
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.