Closed
Bug 300279
Opened 19 years ago
Closed 16 years ago
specific URL reliably crashes Mozilla 1.7.8 during loading
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: eponymousalias, Unassigned)
References
()
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.8) Gecko/20050512 Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.8) Gecko/20050512 Loading the http://docs.sun.com/source/801-6735/801-6735.book URL reliably crashes Mozilla 1.7.8 (as it did with 1.7.6 before that). This is on a machine with 2GB memory and nothing else of significance running, so it's not an out-of-memory problem. This is a fresh install of Mozilla, so no non-default plugins are involved. Reproducible: Always Steps to Reproduce: 1.Load the indicated URL. 2.Wait a 10-15 seconds while the core file is written out. 3. Actual Results: Mozilla crashes. Expected Results: Not crash; produce some kind of viewable error message.
It doesn't crash for me Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.8) Gecko/20050511 or Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b3) Gecko/20050709 Firefox/1.0+ -- The page probably isn't displaying as the author intended it to though.
It is an xml 'book' document http://docs.sun.com/source/DSCHelp/p5.html
There is an xml validator from w3.org (http://www.w3.org/2001/03/webdata/xsv) . Running the URL given in this bug report through it yields some errors or warnings. "Error: can't retrieve "http://docs.sun.com/source/801-6735/ab1.dtd": 404 Not found" Maybe that is something like a stylesheet that allows the page to be properly displayed ? Just guessing wildly.
Comment 4•19 years ago
|
||
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b3) Gecko/20050709 SeaMonkey/1.0a Page Info says the document is served as text/plain, and so I see the start of the file: <!DOCTYPE ab1 PUBLIC "-//Sun Microsystems//DTD AB1 V1.0//EN" "ab1.dtd"> <xhtml xmlns:dsc="http://docs.sun.com/xml"><title xmlns="http://docs.sun.com/xml">Standards Conformance Reference Manual</title><div level="1" source="Cover" type="cover"><dsc:label>Cover</dsc:label> ...
reporter: whose build of mozilla are you using? can you make the core available so that we can poke that group with it? if you run: ./mozilla -g target core _corefile_ where what .so's does it list?
erm, you're almost certainly using dbx not gdb, so that should be: ./mozilla -g -d dbx core _corefile_ where
| Reporter | ||
Comment 7•19 years ago
|
||
I don't quite follow the instructions given in comments #5 and
#6 (the gdb form brings up a window I don't know how to manipulate,
and the dbx form won't accept the commands given), but I believe
I'm being asked for a stack trace and ldd output.
The build is the one distributed on the Mozilla site:
mozilla1.7.8-sparc-sun-solaris2.10-gtk2+xft.tar.bz2
The stack trace from the core file is useless. The program
segfaulted and the stack is corrupted, so a gdb "where" command
shows useless values. gdb 6.2.1 shows:
Core was generated by `/data1/3rdparty/mozilla/mozilla-bin'.
Program terminated with signal 11, Segmentation fault.
#0 0xfe6a0358 in ?? ()
(gdb) where
#0 0xfe6a0358 in ?? ()
#1 0xfe6a0504 in ?? ()
Previous frame identical to this frame (corrupt stack?)
The libraries being used by this binary are:
% ldd /data1/3rdparty/mozilla/mozilla-bin
libmozjs.so => /data1/3rdparty/mozilla/libmozjs.so
libplds4.so => /data1/3rdparty/mozilla/libplds4.so
libplc4.so => /data1/3rdparty/mozilla/libplc4.so
libnspr4.so => /data1/3rdparty/mozilla/libnspr4.so
libpthread.so.1 => /lib/libpthread.so.1
libdl.so.1 => /lib/libdl.so.1
librt.so.1 => /lib/librt.so.1
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0
libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0
libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0
libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0
libm.so.2 => /lib/libm.so.2
libpangoxft-1.0.so.0 => /usr/lib/libpangoxft-1.0.so.0
libpangox-1.0.so.0 => /usr/lib/libpangox-1.0.so.0
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0
libX11.so.4 => /usr/openwin/lib/libX11.so.4
libsocket.so.1 => /lib/libsocket.so.1
libnsl.so.1 => /lib/libnsl.so.1
libCstd.so.1 => /usr/lib/libCstd.so.1
libCrun.so.1 => /usr/lib/libCrun.so.1
libw.so.1 => /lib/libw.so.1
libthread.so.1 => /lib/libthread.so.1
libc.so.1 => /lib/libc.so.1
libaio.so.1 => /lib/libaio.so.1
libmd5.so.1 => /lib/libmd5.so.1
libXft.so.2 => /usr/openwin/lib/libXft.so.2
libfreetype.so.6 => /usr/sfw/lib/libfreetype.so.6
libXrender.so.1 => /usr/sfw/lib/libXrender.so.1
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1
libmlib.so.2 => /usr/lib/libmlib.so.2
libXrandr.so.2 => /usr/X11/lib/libXrandr.so.2
libXi.so.5 => /usr/openwin/lib/libXi.so.5
libXext.so.0 => /usr/openwin/lib/libXext.so.0
libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0
libmp.so.2 => /lib/libmp.so.2
libscf.so.1 => /lib/libscf.so.1
libexpat.so.0 => /usr/sfw/lib/libexpat.so.0
libz.so.1 => /usr/lib/libz.so.1
libdoor.so.1 => /lib/libdoor.so.1
libuutil.so.1 => /lib/libuutil.so.1
/data1/3rdparty/mozilla/cpu/sparcv8plus/libnspr_flt4.so
/usr/lib/cpu/sparcv8plus/libCstd_isa.so.1
/platform/SUNW,Ultra-2/lib/libc_psr.so.1
/platform/SUNW,Ultra-2/lib/libmd5_psr.so.1
/usr/lib/cpu/sparcv8plus+vis/libmlib.so.2
This is being run on an Ultra-2 running stock Solaris 10 FCS,
wth no further patches applied. If it matters, I'm running this
under CDE, not Gnome.
Comment 8•17 years ago
|
||
1.7.x is out of date and unmaintained. Could you try a recent version of SeaMonkey or nightly (http://www.seamonkey-project.org/releases/) please?
| Reporter | ||
Comment 9•17 years ago
|
||
The original bug report is on Solaris, where I run all the time. I'd love to test there, but as it happens I've been trying on and off for several weeks to get the current SeaMonkey code built (now on a recent OpenSolaris release), without success. I suppose the failure to build on this platform should itself be filed as a bug ...
Comment 10•17 years ago
|
||
(In reply to comment #9) > The original bug report is on Solaris, where I run all the time. I'd love Althought MozillaAS v1.7.x is not supported anymore., can you reproduce with MozillaAS v1.7.13 ? > to test there, but as it happens I've been trying on and off for several > weeks to get the current SeaMonkey code built (now on a recent OpenSolaris Can you reproduce with SeaMonkey v1.1.9 ? > release), without success. I suppose the failure to build on this > platform should itself be filed as a bug ... Probably: file a bug, with details on what brake youre build process.
Keywords: crash
Version: unspecified → 1.7 Branch
Comment 11•17 years ago
|
||
(1 month later) No (more) reply from reporter. (Would have been "Incomplete", now is) R.Invalid Reopen if you can reproduce with any (current) build.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 12•17 years ago
|
||
The bug still appears with SeaMonkey v1.1.9 (SeaMonkey crashes with a core dump). Tested on Solaris 10 SPARC.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Comment 14•16 years ago
|
||
Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20070606 It works well for me.
Comment 15•16 years ago
|
||
Changing Version to SeaMonkey 1.1.x according to comment #12. (Mozilla 1.7 is obsolete and unsupported by now.)
Version: 1.7 Branch → SeaMonkey 1.1 Branch
Comment 16•16 years ago
|
||
Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.8.1.15) Gecko/20080710 SeaMonkey/1.1.10 It works well too.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago → 16 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•