If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Crash using existing profile with Mail/News + Classic Theme on November builds

RESOLVED INCOMPLETE

Status

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

People

(Reporter: Christopher Aillon (sabbatical, not receiving bugmail), Unassigned)

Tracking

({crash})

Trunk
x86
Linux
crash

Firefox Tracking Flags

(Not tracked)

Details

Profile 1 is Modern Theme, Profile 2 is Classic Theme

Using Linux 2001-10-31-21:
  Start MailNews with Profile 1.    No crash.
  Start MailNews with Profile 2.    No crash.

Using Linux 2001-11-01-06 and later:
  Start MailNews with Profile 1.    No crash.
  Start MailNews with Profile 2.    CRASH.

I have a talkback ID TB37730262Q from this.

I was able to repeatedly crash just launching MailNews on all builds after
11-01-06 (the TB I submitted is from 2001-11-07-21). I then switched Profile 2
to Modern Theme and launched the app, it worked.  I switched back to Classic
Theme and tried again and it also worked and now I can't reproduce it anymore.

Not sure what caused the crash, so I'll leave it for you guys to determine what
to do with it.  But I shouldn't have had to switch themes just to get mailnews
to not crash...

Comment 1

16 years ago
I've been coding in mailnews for the past several hours, using the Classic theme
in a 0900GMT linux build. I have seen no crashes at all.
Keywords: crash

Comment 2

16 years ago
are you still able to reproduce this?
Status: NEW → ASSIGNED

Comment 3

15 years ago
Hello,
I had the same problems, a couple of time. A found a solution which worked at
least 1 time:

Go to /home/you/.mozilla/your_profile
Move XUL.mfasl to XUL.mfasl_temp or so and start mozilla with
mozilla -p your_profile 

Here is the console output:
I am running Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826

mmap2(NULL, 1635319808, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= -1 ENOMEM (Cannot allocate memory)
brk(0x69a54000)                         = 0x82c4000
mmap2(NULL, 2097152, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0)
= 0x41810000
munmap(0x41810000, 983040)              = 0
munmap(0x41a00000, 65536)               = 0
mmap2(0x41900000, 32768, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x41900000
mmap2(NULL, 1635319808, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= -1 ENOMEM (Cannot allocate memory)
mmap2(NULL, 1635319808, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= -1 ENOMEM (Cannot allocate memory)
open("/usr/lib/mozilla-1.1/libgcc_s.so.1", O_RDONLY) = -1 ENOENT (No such file
or directory)
open("/usr/lib/mozilla-1.1/plugins/libgcc_s.so.1", O_RDONLY) = -1 ENOENT (No
such file or directory)
open("/etc/ld.so.cache", O_RDONLY)      = 15
fstat64(15, {st_mode=S_IFREG|0644, st_size=62680, ...}) = 0
old_mmap(NULL, 62680, PROT_READ, MAP_PRIVATE, 15, 0) = 0x41810000
close(15)                               = 0
open("/lib/libgcc_s.so.1", O_RDONLY)    = 15
read(15, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0@\23\0\000"..., 1024) =
1024
fstat64(15, {st_mode=S_IFREG|0755, st_size=33576, ...}) = 0
old_mmap(NULL, 32464, PROT_READ|PROT_EXEC, MAP_PRIVATE, 15, 0) = 0x41820000
mprotect(0x41827000, 3792, PROT_NONE)   = 0
old_mmap(0x41827000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 15,
0x7000) = 0x41827000
close(15)                               = 0
munmap(0x41810000, 62680)               = 0
--- SIGSEGV (Segmentation fault) ---
unlink("/home/ME/.mozilla/ME/blabla.slt/lock") = 0
Product: Browser → Seamonkey

Updated

13 years ago
Assignee: sspitzer → mail
Status: ASSIGNED → NEW
Christopher, 
jg,
can you create this problem with SM 1.x or trunk build?
QA Contact: esther
no response
closing incomplete
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.