[apport] firefox-bin crashed with SIGSEGV

[forteller]

Binary package hint: firefox

This kind of crash have happened many times before. It goes like this:
1. I have lots of tabs open (25-30).
2. I submit a comment on my WordPress blog which uses the theme K2 (not the newest version). K2 uses some sort of AJAX to submit comments.
3. The second I've clicked the submit button I Ctrl+Tab or Ctrl+Shift+Tab to another Tab.
4. Firefox crashes (not every time I do this, but too many times.

(my blog is located at blogg.forteller.net if that is of any help, but you won't be able to read it, it's in Norwegian.. :))

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Mar 12 23:08:39 2007
Disassembly: 0xb7fe5410:
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/firefox/firefox-bin
Package: firefox 2.0.0.2+1-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox/firefox-bin
ProcCwd: /home/forteller
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
Signal: 11
SourcePackage: firefox
Stacktrace: #0 0xb7fe5410 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Uname: Linux forteller-laptop 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

[Brian Murray (brian-murray)]

StacktraceTop:_start () from /lib64/ld-linux-x86-64.so.2

[Brian Murray (brian-murray)]

I seem to have done the retrace on x86_64, I'm fixing it now.

[Brian Murray (brian-murray)]

StacktraceTop:?? ()

[John Vivirito (gnomefreak)]

Assigning to hjmf to see if he can get a better stacktrace.

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

> Assigning to hjmf to see if he can get a better stacktrace.

--- stack trace ---
#0 0xffffe410 in ?? ()
--- end of stack trace ---

I've seen 4-5 reports with this problem (such retrace). Maybe the problem is related to when the report is generated, I mean that the problem is with apport initial process... don't know.

This happens only on feisty's reported bugs with just "CoreDump.gz, Dependencies.txt, ProcMaps.txt, ProcStatus.txt and Registers.txt" attached. Are always reports named "[apport] firefox-bin crashed with SIGSEGV" when generated instead of the usual "[apport] firefox-bin crashed with SIGSEGV in __kernel_vsyscall()"

[Alexander Sack (asac)]

On Sat, Mar 17, 2007 at 12:31:09PM -0000, Hilario J. Montoliu (hjmf) wrote:
> > Assigning to hjmf to see if he can get a better stacktrace.
>
> --- stack trace ---
> #0 0xffffe410 in ?? ()
> --- end of stack trace ---
>
> I've seen 4-5 reports with this problem (such retrace). Maybe the
> problem is related to when the report is generated, I mean that the
> problem is with apport initial process... don't know.
>
> This happens only on feisty's reported bugs with just "CoreDump.gz,
> Dependencies.txt, ProcMaps.txt, ProcStatus.txt and Registers.txt"
> attached. Are always reports named "[apport] firefox-bin crashed with
> SIGSEGV" when generated instead of the usual "[apport] firefox-bin
> crashed with SIGSEGV in __kernel_vsyscall()"

So how does it usually happen that just those files are available? Has
attaching only those been the default once? In that case it might as
well just mean: old report -> no proper dbgsym packages -> bad
retrace?

 - Alexander

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

El dom, 18-03-2007 a las 16:23 +0000, Alexander Sack escribió:
> On Sat, Mar 17, 2007 at 12:31:09PM -0000, Hilario J. Montoliu (hjmf) wrote:
> > > Assigning to hjmf to see if he can get a better stacktrace.
> >
> > --- stack trace ---
> > #0 0xffffe410 in ?? ()
> > --- end of stack trace ---
> >
> > I've seen 4-5 reports with this problem (such retrace). Maybe the
> > problem is related to when the report is generated, I mean that the
> > problem is with apport initial process... don't know.
> >
> > This happens only on feisty's reported bugs with just "CoreDump.gz,
> > Dependencies.txt, ProcMaps.txt, ProcStatus.txt and Registers.txt"
> > attached. Are always reports named "[apport] firefox-bin crashed with
> > SIGSEGV" when generated instead of the usual "[apport] firefox-bin
> > crashed with SIGSEGV in __kernel_vsyscall()"
>
> So how does it usually happen that just those files are available? Has
> attaching only those been the default once?

I don't know. Just seen only in those reports.

> In that case it might as
> well just mean: old report -> no proper dbgsym packages -> bad
> retrace?

I don't think so. Reporters package versions seem to be the ones
expected the day the crash was reported (ie firefox 2.0.0.2+1-0ubuntu1)

[Freddy Martinez (freddymartinez9)]

look for another retrace to come through.

[Apport retracing service (apport)]

StacktraceTop:?? ()

[John Vivirito (gnomefreak)]

Taking for retrace.

[John Vivirito (gnomefreak)]

can you please list all extentions/themes/addons that are installed please.

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.