[feisty] Firefox Crashed -- libflashplayer

Bug #93358 reported by Viggo
2
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Incomplete
Undecided
Mozilla Bugs

Bug Description

Binary package hint: firefox

error appeared after reboot:
I was running updates.
After updates was done, I rebooted as requested by the updater. Firefox was running when commencing reboot.
When the machine had rebooted, the crash report appeared.

ProblemType: Crash
Architecture: i386
Date: Sun Mar 18 12:48:50 2007
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/vn
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 vn-media 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Viggo (viggo) wrote :
Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote :

Thank you Viggo for this report.

Can you reproduce the bug? If so, which are the steps that cause the crash?

Taken report to retrace

Changed in firefox:
assignee: nobody → hmontoliu
status: Unconfirmed → Needs Info
description: updated
Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote : Re: [feisty] Firefox Crashed

Retrace done

...
#4 0xb7dda460 in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0
#5 0xaed3b858 in ?? () from /home/vn/.mozilla/plugins/libflashplayer.so
#6 0xab103024 in ?? ()
...

Changed in firefox:
assignee: hmontoliu → mozilla-bugs
Revision history for this message
Viggo (viggo) wrote : SV: [Bug 93358] Re: error appeared after reboot

Hi

To clarify: I did not experience any error, only the crash report.

Steps to reproduce:
1: Launch Firefox
2: Enter www.youtube.com
3: Start a video
4: Reboot computer while video is playing.

I managed to do the above several times, producing the Crash report.
The Crash report is unfortunately(?) not appearing any more now.

---
Viggo Normann

-----Opprinnelig melding-----
Fra: <email address hidden> [mailto:<email address hidden>]På vegne av
Hilario J. Montoliu (hjmf)
Sendt: 18. mars 2007 14:12
Til: <email address hidden>
Emne: [Bug 93358] Re: error appeared after reboot

Thank you Viggo for this report.

Can you reproduce the bug? If so, which are the steps that cause the
crash?

Taken report to retrace

** Changed in: firefox (Ubuntu)
     Assignee: (unassigned) => Hilario J. Montoliu (hjmf)
       Status: Unconfirmed => Needs Info

** Summary changed:

- error appeared after reboot
+ [feisty] Firefox Crashed

** Description changed:

  Binary package hint: firefox

+ error appeared after reboot:
  I was running updates.
  After updates was done, I rebooted as requested by the updater. Firefox was running when commencing reboot.
  When the machine had rebooted, the crash report appeared.

  ProblemType: Crash
  Architecture: i386
  Date: Sun Mar 18 12:48:50 2007
  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/vn
  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 vn-media 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686 GNU/Linux
  UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

** Tags added: mt-needretrace

--
[feisty] Firefox Crashed
https://launchpad.net/bugs/93358

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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