Spontaneous crash at securityfocus

VERIFIED DUPLICATE of bug 101365

Status

()

Core
ImageLib
VERIFIED DUPLICATE of bug 101365
17 years ago
17 years ago

People

(Reporter: Tet, Assigned: Stuart Parmenter)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

17 years ago
Mozilla-0.9.4 spontaneously crashes when visiting the above URL.
The page will finish loading, and then a short period of time
later, the browser process will die. The same behaviour was also
observed with previous versions of Mozilla (I tried 0.9.2).

Comment 1

17 years ago
Might be dupe of bug 101365.

Reporter,

Can you use a Talkback-enabled build available here:
http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-i686-pc-linux-gnu-sea.tar.gz
and report a Talkback ID when crashing.
Do you have Java or Flash installed ?
(Reporter)

Comment 2

17 years ago
Flash installed, but no Java. However, I tried removing the flash
plugin, and it still crashes. Talkback IDs:

  TB35846534H  (with flash)
  TB35847433W  (with flash)
  TB35852616Y  (without flash)
Tet

Comment 3

17 years ago
Asa, can you retreive talkback data ?
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 4

17 years ago
Incident ID 35847433
Stack Signature libX11.so.6 + 0x2102f (0x403b102f) f4e0ddf9
Bug ID
Trigger Time 2001-09-25 03:27:45
Email Address tet@accucard.com
User Comments Just reading the page. It had finished loading, and after a few
seconds (maybe a minute or so), the browser just died. Note that this is
repeatable by going to the same site.
Build ID 2001091311
Product ID Netscape6.20
Platform ID LinuxIntel
Trigger Reason SIGSEGV: Segmentation Fault: (signal 11)
Stack Trace
libX11.so.6 + 0x2102f (0x403b102f)
nsImageGTK::DrawToImage()
gfxImageFrame::DrawTo()
imgContainer::DoComposite()
imgContainer::Notify()
nsTimerGtk::FireTimeout()
process_timers()
TimerCallbackFunc()
libglib-1.2.so.0 + 0x12731 (0x4036e731)
libglib-1.2.so.0 + 0x117f3 (0x4036d7f3)
libglib-1.2.so.0 + 0x11dd9 (0x4036ddd9)
libglib-1.2.so.0 + 0x11f8c (0x4036df8c)
libgtk-1.2.so.0 + 0x94803 (0x40282803)
nsAppShell::Run()
nsAppShellService::Run()
main1()
main()
libc.so.6 + 0x1c177 (0x404b0177) 

and without flash:
Incident ID 35852616
Stack Signature libc.so.6 + 0x80017 (0x40514017) bbbb7e01
Bug ID
Trigger Time 2001-09-25 05:54:49
Email Address tet@accucard.com
User Comments Just leaving the page to go to a new one (by typing in a new URL)
Build ID 2001091311
Product ID Netscape6.20
Platform ID LinuxIntel
Trigger Reason SIGSEGV: Segmentation Fault: (signal 11)
Stack Trace
libc.so.6 + 0x80017 (0x40514017)
libc.so.6 + 0x7fd59 (0x40513d59)
libstdc++-libc6.1-1.so.2 + 0x3132e (0x405f532e)
nsImageGTK::~nsImageGTK()
nsImageGTK::Release()
nsCOMPtr_base::~nsCOMPtr_base()
gfxImageFrame::~gfxImageFrame()
gfxImageFrame::Release()
nsSupportsArray::Clear()
imgContainer::~imgContainer()
imgContainer::Release()
nsCOMPtr_base::~nsCOMPtr_base()
imgRequest::~imgRequest()
imgRequest::Release()
EventHandler()
PL_HandleEvent()
PL_ProcessEventsBeforeID()
processQueue()
nsVoidArray::EnumerateForwards()
nsAppShell::ProcessBeforeID()
handle_gdk_event()
libgdk-1.2.so.0 + 0x17e4f (0x4033ae4f)
libglib-1.2.so.0 + 0x117f3 (0x4036d7f3)
libglib-1.2.so.0 + 0x11dd9 (0x4036ddd9)
libglib-1.2.so.0 + 0x11f8c (0x4036df8c)
libgtk-1.2.so.0 + 0x94803 (0x40282803)
nsAppShell::Run()
nsAppShellService::Run()
main1()
main()
libc.so.6 + 0x1c177 (0x404b0177) 
Assignee: asa → pavlov
Component: Browser-General → ImageLib
QA Contact: doronr → tpreston

Comment 5

17 years ago
Sig11 might be a hardware problem. See FAQ here: http://www.bitwizards.nl/sig11/

Reporter, do you have stability problems with this machine ? You might want to
try running RC5 ( http://www.distributed.net/ ) and compiling kernel at the same
time to trigger a Sig11. Changing RAM can improve too.
(Reporter)

Comment 6

17 years ago
No, no stability problems whatsoever. Rock solid, including during kernel
compilations etc. I'd be *very* surprised if this turned out to be a hardware
glitch. Apart from anything else, it's 100% reproducible at the same site.
Hardware faults tend to be more intermittent.

Comment 7

17 years ago
Marking bug as dup of bug 101365 to allow tracking a unique bug report. I'll add
the talkback data to bug 101365.

*** This bug has been marked as a duplicate of 101365 ***
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → DUPLICATE

Comment 8

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