crash on startup during (possibly at end of) 'opening folder' operation on Inbox (using IMAP) with FLTBOUNDS error after EAGAIN

RESOLVED INCOMPLETE

Status

SeaMonkey
MailNews: Message Display
--
critical
RESOLVED INCOMPLETE
14 years ago
10 years ago

People

(Reporter: Richard A. Mead, Unassigned)

Tracking

Trunk
Sun
Solaris

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Opera/7.23 (X11; SunOS sun4u; U)  [en]
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.5) Gecko/20031222

Opening mail component of Mozilla crashes entire application, without any core 
file being generated.  I've looked for core files in the install directory, my 
home directory, and the current working directory at the time of starting 
Mozilla.  Setting IMAP debug level to 5 shows no errors - last line in log is a 
successful message ending.  Truss output shows no obvious reason for the failure 
- system call of crashing thread just prior to crash is a standard looking 
poll().  I don't believe that any change of configuration of my environment has 
occurred to have triggered this issue, and I have been using this version of 
Mozilla for some time now in this IMAP configuration.  I am able to access my 
e-mail from a Windows 2000 machine using Outlook with IMAP without issues.

Reproducible: Always
Steps to Reproduce:
1. Start Mozilla mail component from command line or from browser component.
2. Wait for 'connecting' then 'authenticating' then 'looking for folders' 
messages to display in status area.
3. See 'opening folder' message in status area until crash occurs.

Actual Results:  
Mozilla crashes from FLTBOUNDS fault resulting in SIGSEGV (SEGV_MAPERR) with no 
core file generated.

Expected Results:  
Mail component finishes refreshing Inbox view and continues normal operation.

End of truss output:

seso2(richmead):7614$truss -aeful /opt/csw/bin/mozilla -nosplash -install -mail 
>~/working/moz.truss 2>&1
seso2(richmead):7615$cd working
seso2(richmead):7616$tail -30 moz.truss
28018/2:	poll(0xFDD0FC68, 3, -1)				= 1
28018/2:	read(33, " *   1 2 4 3   F E T C H".., 4096)	= 4096
28018/2:	write(6, "FA", 1)				= 1
28018/2:	read(33, " 9 - 4 6 5   [ 1 u   -  ".., 4096)	= 4096
28018/2:	read(33, 0x006654F4, 4096)			Err#11 EAGAIN
28018/1:	poll(0x002A2F10, 7, -1)				= 1
28018/1:	read(5, "FA", 1)				= 1
28018/1:	ioctl(4, FIONREAD, 0xFFBFCDEC)			= 0
28018/6:	lwp_park(0xFBC1F630, 0)				Err#62 ETIME
28018/6:	write(6, "FA", 1)				= 1
28018/1:	poll(0x002A2F10, 7, -1)				= 1
28018/2:	poll(0xFDD0FC68, 3, -1)				= 1
28018/2:	read(33, " " M E S S A G E - I D "".., 4096)	= 4096
28018/2:	read(33, " . c o m > ,\r\n       M".., 4096)	= 4096
28018/2:	read(33, 0x0064E4D4, 4096)			Err#11 EAGAIN
28018/1:	    Incurred fault #6, FLTBOUNDS  %pc = 0xFF2B3FB8
28018/1:	      siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
28018/1:	    Received signal #11, SIGSEGV [caught]
28018/1:	      siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
28018/1:	sigprocmask(SIG_SETMASK, 0xFFBFC40C, 0x00000000) = 0
28018/1:	unlink("/home/richmead/.mozilla/richmead/1uv0bsm0.slt/lock") = 
028018/1:	_exit(11)
27991:	waitid(P_PID, 28018, 0xFFBFCEC0, WEXITED|WTRAPPED|WNOWAIT) = 0
27991:	ioctl(0, TIOCGPGRP, 0xFFBFCE7C)			= 0
27991:	ioctl(0, TCGETS, 0x000391D4)			= 0
27991:	waitid(P_PID, 28018, 0xFFBFCEC0, WEXITED|WTRAPPED) = 0
27991:	stat64("core", 0xFFBFCAC0)			Err#2 ENOENT
27991:	brk(0x0003EF88)					= 0
27991:	brk(0x0003ED88)					= 0
27991:	_exit(11)

Updated

14 years ago
OS: SunOS → Solaris
(Reporter)

Comment 1

14 years ago
This is on Solaris 9, Generic_112233-11 on a Blade 1000...
Product: Browser → Seamonkey

Comment 2

13 years ago
same problem here in thunderbird

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050320 Thunderbird/1.0.2
GNU/Linux Kernel 2.6.10 - Pentium III

Comment 3

13 years ago
I found the reason: it was an inaccessible sound device, so thunderbird wasn't
able to play the new mail alert.
(Reporter)

Comment 4

13 years ago
Good news - thanks!

Updated

13 years ago
Assignee: sspitzer → mail
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/
(Reporter)

Comment 6

13 years ago
Given that it involved (apparently) a corrupted mbox, I doubt that I will be
able to easily reproduce the issue...  It seems to have occurred sometime after
encountering the type of corruption that shows up as subject lines not matching
the displayed message body and/or message body being either 'cut off' or
including part of one message followed by the headers and body of the next
message.  Of late, I have been using Mozilla v    1.7 for Sun Java™ Desktop
System, Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20041221 and have
encountered the first of the above issues once or twice, as well as a few
'hangs' of the browser compone (which also hung the e-mail component!) but a
restart of the application seems to have resolved it each time.

I have not (yet?) encountered the same type of corruption as what was occurring
for this bug.

Comment 7

10 years ago
Seems that this hasn't happened again and the information given is apparently not enough to address the problem. --> incomplete
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.