[FEISTY] firefox crashed [@js_Invoke] [@js_InternalInvoke]

[spiffytech]

Binary package hint: firefox

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed May 16 09:15:21 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/brian
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: firefox
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libpthread.so.0
 ?? ()
 ?? ()
 ?? ()
Uname: Linux brian-laptop 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Dennis Francis (dennisfrancis)]

Thank you for reporting this issue.
It would be of great help if you could find out how to reproduce the crash. This webpage [ https://wiki.ubuntu.com/MozillaTeam/Bugs?action=show&redirect=DebuggingFirefox ] has all the info to help you.
Thank you.

[Hilario J. Montoliu (hjmf) (hmontoliu)]

Retrace done.

Extract from retraced stacktrace:
...
#3 <signal handler called>
#4 js_Invoke (cx=0x88e4928, argc=1, flags=2) at jsinterp.c:1446
#5 js_InternalInvoke (cx=0x88e4928, obj=0x8880960,
#6 JS_CallFunctionValue (cx=0x88e4928, obj=0x8880960,
#7 nsJSContext::CallEventHandler (this=0x88e3f48,
#8 nsJSEventListener::HandleEvent (this=0x8796da8,
#9 nsEventListenerManager::HandleEventSubType (this=0x86c9838,
#10 nsEventListenerManager::HandleEvent (this=0x86c9838,
#11 nsXULElement::HandleDOMEvent (this=0x87cf9d8,
#12 nsXULCommandDispatcher::UpdateCommands (this=0x840ab78,
...

[Hilario J. Montoliu (hjmf) (hmontoliu)]

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.

[Hilario J. Montoliu (hjmf) (hmontoliu)]

We have not received any duplicates for some time. Thus, this crash was likely due to some unique plugin extension combination or has been fixed in the meantime. Please, reopen it at any time if you have more related info.

Thanks for your contribution. Don't hesitate to submit new crashes,

H. Montoliu