[FEISTY] firefox crashed [@nsAttrAndChildArray::GetAttr] [@nsXULElement::FindLocalOrProtoAttr]

[Klaus-Dieter]

Binary package hint: firefox

Crashed on sartup. Firefox was not closed before shutdown.

ProblemType: Crash
Architecture: i386
Date: Fri May 25 00:21:17 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/jens
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
Signal: 11
SourcePackage: firefox
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libpthread.so.0
 ?? ()
 ?? ()
 ?? ()
Uname: Linux jensens-rechner 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

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

Retrace done.

Extract from retraced stacktrace:
...
#3 <signal handler called>
#4 nsAttrAndChildArray::GetAttr (this=0x0, aLocalName=0x82cc920,
#5 nsXULElement::FindLocalOrProtoAttr (this=0x9dffd50,
#6 nsXULElement::GetAttr (this=0x9dffd50, aNameSpaceID=0,
#7 nsIFrame::AddCSSMinSize (aState=@0xbfd85ae4, aBox=0x9e04e6c,
#8 nsBoxFrame::GetMinSize (this=0x9e04e6c,
#9 nsSprocketLayout::GetMinSize (this=0x84d58c0,
#10 nsBoxFrame::GetMinSize (this=0x9e04da8,
#11 nsSprocketLayout::GetMinSize (this=0x84d58c0,
#12 nsBoxFrame::GetMinSize (this=0x9dce898,
...

Tagging as mt-confirm for further processing

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

Retraced Thread Stacktrace

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

Thank you Klaus-Dieter for your report,

Is the crash reproducible? If so, can you try to reproduce it in "-safe-mode" and describe the steps that lead to it?

Also, please indicate which extensions/plugins do you have enabled.

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