MASTER firefox crashed [@nsCOMPtr_base::assign_with_AddRef] [@nsWindow::FireDragLeaveTimer] [@nsWindow::DragLeaveTimerCallback]

Bug #103250 reported by fberdayes
10
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Fix Released
High
Mozilla Bugs

Bug Description

Binary package hint: firefox

... [Feisty] Firefox Crash [@ nsCOMPtr_base::assign_with_AddRef ]

firefox

ProblemType: Crash
Architecture: i386
Date: Thu Apr 5 11:21:56 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/firefox/firefox-bin
Package: firefox 2.0.0.3+1-0ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox/firefox-bin
ProcCwd: /home/mariayfran
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=es_ES.UTF-8
Signal: 11
SourcePackage: firefox
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libpthread.so.0
 ?? ()
 ?? ()
 ?? ()
Uname: Linux mariayfran-desktop 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Extracted from symbolized stacktrace:
(file: http://launchpadlibrarian.net/7154668/%3Cfdopen%3E)
...
#3 <signal handler called>
#4 nsCOMPtr_base::assign_with_AddRef (this=0x8fc97c8, rawPtr=0x0)
#5 nsWindow::FireDragLeaveTimer (this=0x8fc96e0)
#6 nsWindow::DragLeaveTimerCallback (aTimer=0x8f857c8,
#7 nsTimerImpl::Fire (this=0x8f857c8) at nsTimerImpl.cpp:394
#8 handleTimerEvent (event=0xb0801a20) at nsTimerImpl.cpp:459
#9 PL_HandleEvent (self=0xb0801a20) at plevent.c:688
#10 PL_ProcessPendingEvents (self=0x80cf9c8) at plevent.c:623
#11 nsEventQueueImpl::ProcessPendingEvents (this=0x80cf980)
#12 event_processor_callback (source=0x8182c30,
...

Tags: mt-upstream
Revision history for this message
fberdayes (fberdayes76) wrote :
Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote :

Thank you fberdayes for taking the time to report this crash.

Can you describe how did it happen? Also, if it is reproducible, please submit the steps to force the crash.
Which extensions/plugins do you have enabled

Thank you in advance.

Changed in firefox:
assignee: nobody → mozilla-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote : Retraced Stacktrace

Retrace done:
...
#3 <signal handler called>
#4 nsCOMPtr_base::assign_with_AddRef (this=0x8fc97c8, rawPtr=0x0)
    at ./../glue/nsCOMPtr.h:531

#5 0xb67d5ab5 in nsWindow::FireDragLeaveTimer (this=0x8fc96e0)
    at ../../../dist/include/xpcom/nsCOMPtr.h:713

#6 0xb67d5b11 in nsWindow::DragLeaveTimerCallback (aTimer=0x8f857c8,
    aClosure=0x8fc96e0) at nsWindow.cpp:4343

#7 0xb7ee39ad in nsTimerImpl::Fire (this=0x8f857c8) at nsTimerImpl.cpp:394
 now = 3238844252
 timeout = 3238844062
#8 0xb7ee4268 in handleTimerEvent (event=0xb0801a20) at nsTimerImpl.cpp:459
 timer = (nsTimerImpl *) 0x8f857c8
#9 0xb7edf417 in PL_HandleEvent (self=0xb0801a20) at plevent.c:688
...

Tagging as mt-confirm for further processing

Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote : Retraced Thread Stacktrace

Retraced Thread Stacktrace

Changed in firefox:
importance: Undecided → High
Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote : Re: [Feisty] Firefox Crash [@ nsCOMPtr_base::assign_with_AddRef ]

Is this still an issue for you? We are trying to sort this issue and would like to know if this still happens.

If it can be reproduced, please describe the steps to do it.

Thanks in advance.

Changed in firefox:
status: Needs Info → Confirmed
description: updated
Changed in firefox:
status: Confirmed → Needs Info
Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote :

A master should be at least in confirmed state

Changed in firefox:
status: Incomplete → Confirmed
Revision history for this message
Alexander Sack (asac) wrote :

should be fixed upstream by security/stability updates.

Changed in firefox:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.