190883 - Mozilla 1.2.1 crashed, and doesn't start-up now.

Status: VERIFIED DUPLICATE of bug 169777

(SeaMonkey :: General, defect)

Description

[luis fernandes]

User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1) Gecko/20020827
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1) Gecko/20020827

I was running mozilla 1.2.1 and it crashed. When I tried to re-start it again I
wasn't able to. I am using mozilla-1.1 to report this.

When I try to run mozilla 1.2.1, the profile manager comes up, I chhose a
profile and then it exits. Here is the last bit of the truss:

read(3, " / u s r / l o c a l / b".., 128)      = 22
read(3, 0xFFBEF0C8, 128)                        = 0
ioctl(3, TCGETA, 0xFFBEEF4C)                    Err#22 EINVAL
ioctl(3, TCGETA, 0xFFBEEFAC)                    Err#22 EINVAL
close(3)                                        = 0
waitid(P_PID, 10634, 0xFFBEEFA8, WEXITED|WTRAPPED) = 0
stat64("/usr/local/bin/md5sum", 0xFFBEEFD0)     = 0
access("/usr/local/bin/md5sum", 9)              = 0
stat64("core", 0xFFBEEE38)                      Err#2 ENOENT
fork()                                          = 10636
waitid(P_PID, 10636, 0xFFBEF188, WEXITED|WTRAPPED|WNOWAIT) (sleeping...)
X Error of failed request:  BadAccess (attempt to access private resource denied
)
  Major opcode of failed request:  131 (MIT-SHM)
  Minor opcode of failed request:  1 (X_ShmAttach)
  Serial number of failed request:  1727
  Current serial number in output stream:  1728
waitid(P_PID, 10636, 0xFFBEF188, WEXITED|WTRAPPED|WNOWAIT) = 0
ioctl(0, TIOCGPGRP, 0xFFBEF144)                 = 0
ioctl(0, TCGETS, 0x000391B8)                    = 0
waitid(P_PID, 10636, 0xFFBEF188, WEXITED|WTRAPPED) = 0
stat64("core", 0xFFBEED28)                      Err#2 ENOENT
brk(0x0003E088)                                 = 0
brk(0x0003DE88)                                 = 0
llseek(0, 0, SEEK_CUR)                          = 55840
_exit(1)


Reproducible: Always

Steps to Reproduce:
I can't reproduce this because mozilla 1.2.1 doesn't start-up anymore. 

This is what I did on 1.2.1 (as far as I remember it) for it to crash:
1. http://www.google.ca
2. Click on "Images"
3. Enter search-query: blade 100
4. Click-right on first image and select "Save Image As..."
5. Typed in "/home/faculty/elf/images/mat/b100.gof" (yes "gof") (the Filetype
was "jpeg, jpg, etc...)
6. Hit "Return"


Actual Results:  
Mozilla exited/crashed.

Expected Results:  
Saved the image I was trying to download.

Comment 1

[Matthias Versen [:Matti]]

Reporter:
Can you please try to delete the file "xul.mfl" in your mozilla user profile ?

Comment 2

[Matthias Versen [:Matti]]

via mail : 
>Actually it's "XUL.mfasl" (case matters under Unix).
>After deleting this file, I can start 1.2.1.

I know that *nix is case sensitive but i didn't know that the name is "XUL.mfasl"
Sorry but i hope you can forgive me as win32 user :-)

marking as dupe of bug 169777

*** This bug has been marked as a duplicate of 169777 ***

Comment 3

[luis fernandes]

Mozilla crashed on me again and wouldn't re-start. It crased when I
clicked-right on an image, selected "Save Image As...", and typed-in the
filename in the file-dialog box and hit RETURN.
 

X Error of failed request:  BadAccess (attempt to access private resource denied)
  Major opcode of failed request:  131 (MIT-SHM)
  Minor opcode of failed request:  1 (X_ShmAttach)
  Serial number of failed request:  1649
  Current serial number in output stream:  1650

However, I noticed that GIMP was running when it happened both times. Deleting
the XUL* file wouldn't fix the problem as long as GIMP was running. 

As soon as I quit GIMP and deleted the XUL* file, mozilla started again.

GIMP has to be running for mozilla to crash when I do the above steps.

Note: I do get (and ignore) the warnings mentioned in the README (Gdk-WARNING
**: shmat failed!) but I haven't increased the shared memory segment size--
maybe this has something to do with it as GIMP is GDK also based and uses shm.

I don't know whether this has really been resolved from the emails going back
and forth so I'm re-opening it. If this is wrong, please forgive me and set it
as resolved.

Comment 4

[Matthias Versen [:Matti]]

thids should be a dupe of bug 169777.
Please reopen only if you get this with a recent nightly build.

*** This bug has been marked as a duplicate of 169777 ***

Comment 5

[Daniel Wang]

v