Closed
Bug 89099
Opened 25 years ago
Closed 25 years ago
Browser segfaults at startup
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: jwbaker, Assigned: asa)
References
()
Details
(Keywords: crash)
2001-07-03-11-trunk build for linux, pulled from ftp.mozilla.org. Upon startup,
it crashes with a segmentation fault. mozilla -CreateProfile foo works, but
mozilla -P foo segfaults. mozilla -P brings up the profile dialog, but
segfaults if you actually pick one. Previous nightlies and releases work fine.
My configuration is Linux 2.4.4, XFree86 4.1.0, on Slackware 8.0.
| Reporter | ||
Updated•25 years ago
|
| Reporter | ||
Comment 1•25 years ago
|
||
The 2001-07-03-09-trunk gcc295 build works fine.
Comment 2•25 years ago
|
||
Windows NT Version 4.0 ( Build 1381: Service pack 4)
latest ( 11 am ) nightly build ID: 2001070304
I just had mozilla crash upon click of profile selection at the end of the install.
I then double clicked the icon shortcut on my desktop & it launched AOK -
using the profile I had selected causing the crash AND without asking me
to select a profile
| Reporter | ||
Comment 4•25 years ago
|
||
Could be but that's a hang and this is a crash.
Comment 5•25 years ago
|
||
I cannot reproduce this using today's commercial trunk build
2001-07-03-11-trunk on Windows2000.
| Reporter | ||
Comment 7•25 years ago
|
||
Yes, you're right, and they might be the same bug, for all I know. I'll have to
wait for the next build to find out, since I can't build the lizard at the
moment. Note though that in my case Mozilla crashes at startup with 0, 1, 2, or
more profiles.
Had the same problem with 2001070304 (trunk from 9 am) on win98
After selecting a profile, mozilla crashes.
I'm 'll try the trunk build from 11am now.
Comment 10•25 years ago
|
||
2001-07-03-11-trunk (build id is also 2001070304) works ok.
| Assignee | ||
Comment 11•25 years ago
|
||
anyone got a stacktrace? is talkback catching this?
Keywords: smoketest
Stack trace from the build with which this bug was first reported.
I'm wondering if the dependencies used to generate that build were not correct.
Is the build team still not using compiler-generated dependencies for the
nightly builds?
#0 0x40148bcf in nsXPTCStubBase::Sentinel4 ()
from /export/dbaron/releases/2001-07-03-11-trunk/libxpcom.so
#1 0x40148e4b in nsXPTCStubBase::Sentinel4 ()
from /export/dbaron/releases/2001-07-03-11-trunk/libxpcom.so
#2 0x40149ee9 in NR_RegGetKey ()
from /export/dbaron/releases/2001-07-03-11-trunk/libxpcom.so
#3 0x4012db01 in nsRegistry::GetSubtree ()
from /export/dbaron/releases/2001-07-03-11-trunk/libxpcom.so
#4 0x40b1255a in NSGetModule ()
from /export/dbaron/releases/2001-07-03-11-trunk/components/libstrres.so
#5 0x40b137e9 in NSGetModule ()
from /export/dbaron/releases/2001-07-03-11-trunk/components/libstrres.so
#6 0x407cd03d in NSGetModule ()
from /export/dbaron/releases/2001-07-03-11-trunk/components/liburiloader.so
#7 0x407029c4 in NSGetModule ()
from /export/dbaron/releases/2001-07-03-11-trunk/components/libnecko.so
#8 0x40145141 in XPTC_InvokeByIndex ()
from /export/dbaron/releases/2001-07-03-11-trunk/libxpcom.so
#9 0x401368c1 in nsProxyObject::Post ()
from /export/dbaron/releases/2001-07-03-11-trunk/libxpcom.so
#10 0x40132057 in PL_HandleEvent ()
from /export/dbaron/releases/2001-07-03-11-trunk/libxpcom.so
#11 0x40131f73 in PL_ProcessPendingEvents ()
from /export/dbaron/releases/2001-07-03-11-trunk/libxpcom.so
#12 0x40132f08 in nsEventQueueImpl::ProcessPendingEvents ()
from /export/dbaron/releases/2001-07-03-11-trunk/libxpcom.so
#13 0x4090eb63 in to_object ()
from /export/dbaron/releases/2001-07-03-11-trunk/components/libwidget_gtk.so
#14 0x4090e8dd in to_object ()
from /export/dbaron/releases/2001-07-03-11-trunk/components/libwidget_gtk.so
#15 0x4034aaca in g_io_unix_dispatch () from /usr/lib/libglib-1.2.so.0
#16 0x4034c186 in g_main_dispatch () from /usr/lib/libglib-1.2.so.0
#17 0x4034c751 in g_main_iterate () from /usr/lib/libglib-1.2.so.0
#18 0x4034c8f1 in g_main_run () from /usr/lib/libglib-1.2.so.0
#19 0x402705b9 in gtk_main () from /usr/lib/libgtk-1.2.so.0
#20 0x4090f05c in to_object ()
from /export/dbaron/releases/2001-07-03-11-trunk/components/libwidget_gtk.so
#21 0x4068aa5a in NSGetModule ()
from /export/dbaron/releases/2001-07-03-11-trunk/components/libnsappshell.so
#22 0x804f8bf in NS_CreateNativeAppSupport ()
#23 0x8050165 in main ()
#24 0x404459cb in __libc_start_main (main=0x8050038 <main>, argc=2,
argv=0xbffff914, init=0x804b2d0 <_init>, fini=0x8051e78 <_fini>,
rtld_fini=0x4000ae60 <_dl_fini>, stack_end=0xbffff90c)
at ../sysdeps/generic/libc-start.c:92
I do not see this in my own optimized build. I suspect this is a build system
problem with the way the nightly builds are done.
leaf said there was a depend-pass problem in xprint so that the depend pass
wouldn't complete.
My pre-alecf-backout debug build has the profile manager problem that happened
before, and my post-alecf-backout opt build is fine.
Marking this as invalid based on above comments. I think the person reporting
problems on Windows in an earlier build was seeing bug 89060.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•