Closed Bug 51225 Opened 24 years ago Closed 24 years ago

Start up crashes on linux

Categories

(SeaMonkey :: General, defect, P3)

Product:
SeaMonkey
Component:
General
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 51164

People

(Reporter: bogado, Assigned: asa)

Details

(Keywords: crash) 

From Bugzilla Helper:
User-Agent: Mozilla/4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
BuildID: I don't have the build ID, but this is the build in this URL :
ftp://ftp.mozilla.org/pub/mozilla/nightly/2000-09-01-10-M18/mozilla-i686-pc-linux-gnu.tar.gz

The browser don't start and simply crashes.

Reproducible: Always
Steps to Reproduce:
I simply run it. 

Actual Results:  [bogado@victor bogado]$ /opt/package/mozilla
/opt/package/run-mozilla.sh /opt/package/mozilla-bin
MOZILLA_FIVE_HOME=/opt/package
  LD_LIBRARY_PATH=/opt/package
     LIBRARY_PATH=/opt/package
       SHLIB_PATH=/opt/package
          LIBPATH=/opt/package
       ADDON_PATH=/opt/package
      MOZ_PROGRAM=/opt/package/mozilla-bin
      MOZ_TOOLKIT=
        moz_debug=0
     moz_debugger=


Oh no!  /opt/package/mozilla-bin just dumped a core file.

Do you want to debug this ? You need a lot of memory for this, so watch out ?
[y/n] y

Expected Results:  The browser window show. 						

Here is a backtrace from the core file : 
#0  0x400b0870 in nsComponentManagerImpl::Shutdown ()
   from /opt/package/libxpcom.so
#1  0x40081e02 in NS_ShutdownXPCOM () from /opt/package/libxpcom.so
#2  0x804e06b in JS_PushArguments ()
#3  0x402579cb in __libc_start_main (
    main=0x804df4c <JS_PushArguments+11252>, argc=1, argv=0xbffffaa4, 
    init=0x804ae78 <_init>, fini=0x805458c <_fini>, 
    rtld_fini=0x4000ae60 <_dl_fini>, stack_end=0xbffffa9c)
    at ../sysdeps/generic/libc-start.c:92
I think this may be a dupe, but I can't start up Mozilla on my Redhat 6.1
system, either
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: crash
Same here.... started yesterday. Continues with today's build.  I don't get a
core dump, it just doesn't start up.  Also using redhat 6.1 with all updates
applied. Including the glibc security update that I installed yesterday. Don't
know if that has anything to do with this. One of the changes had to do with how
LD_LIBRARY_PATH is handled.

If I keep trying to execute mozilla, eventually it starts. About once out of
every 5 attempts. No error messages, per se, it just returns to the shell prompt
and I try again...

[kdowling@ken] ~ $ mozilla
/home/kdowling/mozilla/package/run-mozilla.sh
/home/kdowling/mozilla/package/mozilla-bin
MOZILLA_FIVE_HOME=/home/kdowling/mozilla/package
  LD_LIBRARY_PATH=/home/kdowling/mozilla/package
     LIBRARY_PATH=/home/kdowling/mozilla/package
       SHLIB_PATH=/home/kdowling/mozilla/package
          LIBPATH=/home/kdowling/mozilla/package
       ADDON_PATH=/home/kdowling/mozilla/package
      MOZ_PROGRAM=/home/kdowling/mozilla/package/mozilla-bin
      MOZ_TOOLKIT=
        moz_debug=0
     moz_debugger=
WEBSHELL+ = 1
WEBSHELL+ = 2
CSSLoaderImpl::LoadAgentSheet: Load of URL
'file:///home/kdowling/.mozilla/default/chrome/userChrome.css' failed.  Error
code: 16389
CSSLoaderImpl::LoadAgentSheet: Load of URL
'file:///home/kdowling/.mozilla/default/chrome/userContent.css' failed.  Error
code: 16389


I reinstalled the redhat 6.1 glibc rpms and no more startup problem.  I've read
on various newsgroups that folks are having numerous problems with RedHat's new
glibc security fix update.
I have not insalled the glibc update, and Mozilla does not start for me.   
Actually, I get no core dump or anything useful, either.   Here's what I get:

[wd@dormcam package]$ ./mozilla
./run-mozilla.sh ./mozilla-bin
MOZILLA_FIVE_HOME=.
  LD_LIBRARY_PATH=.
     LIBRARY_PATH=.
       SHLIB_PATH=.
          LIBPATH=.
       ADDON_PATH=.
      MOZ_PROGRAM=./mozilla-bin
      MOZ_TOOLKIT=
        moz_debug=0
     moz_debugger=
[wd@dormcam package]$
Severity: critical → blocker
take a look at bug 51164
And bug 41414 which sounds like it might be the 'real' problem.

Works fine for me under debian unstable with all the latest glibc stuff. May be
specific to the new RH libraries.
well it's intermittant. Sometimes it'll start right away - other times i have to
kickstart it several times to get it going.
This happened to me, I deleted my old .mozilla directory and it worked fine.
i've noticed that if i start it with ./mozilla -g -d gdb
and then type "run" right away, it will never start but fails - usually with
wildly different errors each time: sometimes a crash, sometimes a file it didn't
find,
WEBSHELL+ = 2
[New Thread 1204]
[New Thread 1205]
CSSLoaderImpl::DidLoadStyle: Load of URL 'chrome://communicator/skin/menu.css'
failed.  Error code: 16389

Program received signal SIGSEGV, Segmentation fault.
0x82ebc50 in ?? ()

----

WEBSHELL+ = 2
[New Thread 1226]
CSSLoaderImpl::DidLoadStyle: Load of URL
'chrome://communicator/skin/formatting.css' failed.  Error code: 16389

Program received signal SIGSEGV, Segmentation fault.
0x400c0fc4 in nsProxyEventObject::GetNewOrUsedProxy ()
   from /tmp/package/./libxpcom.so

----

BUTR: If i do ./mozilla -g -d gdb and then WAIT for around one minute before
typing "run", it will start fine. Before that minute has passed there is always
some disk activity - if i wait for that rattle and type run - it starts.

An uneducated guess would be that there are events that can get out of synch
during startup.


bug 51267 "mozilla failing to load some stylesheets from the JAR files."
seems relevant.
Errors about loading userChrome.css and userContent.css are not fatal.  If you
don't have those files, you see those messages.

I'm going to mark this a dup since more people are tracking the other bug,
although this one may have better information.

*** This bug has been marked as a duplicate of 51164 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Verified dupe of recent bug 51164: "Linux builds crashing on startup for some
people"
Status: RESOLVED → VERIFIED
Kenneth, I'm not sure but I think you might be seeing bug 41414, which is caused
by a particular version of glibc.  Since you said you had the problem after
upgrading your glibc and then it disappeared after downgrading that seems the
most likely answer.

The other people here I dunno. RKAa's problems sound very similar to the
symptoms of bug 41414 also.  Everyone else here should make sure that have a
clean install, remove the old ~/.mozilla/, and make sure you have write access
to the installation directory once to create some necessary files.  See bug
42184 for more info on that.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.