browser crash at sun.com

VERIFIED DUPLICATE of bug 120300

Status

()

Core
DOM: Events
--
critical
VERIFIED DUPLICATE of bug 120300
16 years ago
16 years ago

People

(Reporter: Kervin, Assigned: joki (gone))

Tracking

({crash})

Trunk
x86
Linux
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

16 years ago
Don't have a location, could find it after the crash.

Wasn't doing anything special either, a page was loading.

I did get a stack trace with locals.  And from the strace I'm guessing DOM
Events as the component.  

Seems like a pointer got double free'd??

Build ID: 2001122501

[mozilla@bashful mozilla]$ uname -a
Linux bashful 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 i686 unknown
[mozilla@bashful mozilla]$ gcc -v
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.0.2/specs
Configured with: /tmp/gcc-3.0.2/configure --prefix=/usr
Thread model: single
gcc version 3.0.2
[mozilla@bashful mozilla]$ ld -v
GNU ld version 2.11.90.0.8 (with BFD 2.11.90.0.8)
[mozilla@bashful mozilla]$ cat mozilla/.mozconfig
ac_add_options --prefix=/usr/local/mozilla
ac_add_options --enable-extensions=default,irc
ac_add_options --enable-leaky
ac_add_options --enable-jprof
ac_add_options --enable-xpctools
ac_add_options --enable-optimize=-O2
ac_add_options --enable-crypto
ac_add_options --disable-strip
[mozilla@bashful mozilla]$

Updated

16 years ago
Severity: normal → critical
Keywords: crash
(Reporter)

Comment 1

16 years ago
Created attachment 62977 [details]
The full stack trace with locals.


The full stack trace with locals.
(Reporter)

Comment 2

16 years ago
found the URL, http://www.sun.com/software/solaris/programs

I was first at http://www.sun.com/software/solaris/programs/solaris9ea but the
crash occured when I went down one directory
I'm guessing this was just a random crash that happened once, right?

*** This bug has been marked as a duplicate of 120300 ***
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → DUPLICATE
er, that should've been bug 117153, but it doesn't really matter.

Comment 5

16 years ago
verifying
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.