firefox crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firefox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Massive CPU utilization and IO Wait status.. No discernable memory effecs
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: firefox 24.0+build1-
ProcVersionSign
Uname: Linux 3.11.0-7-generic x86_64
NonfreeKernelMo
AddonCompatChec
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
BuildID: 20130917154415
Channel: Unavailable
Date: Thu Sep 19 22:17:34 2013
DefaultProfileB
Cache.Trash (0o755, wrong owner)
Cache.
Cache.
Cache.
Cache.
ExecutablePath: /usr/lib/
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IpRoute:
default via 192.168.1.1 dev wlan0 proto static
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.62 metric 9
MarkForUpload: True
ProcCmdline: /usr/lib/
Profile0PrefSou
prefs.js
/usr/share/
/usr/share/
/usr/share/
Profiles:
Profile0 - LastVersion=
Profile1 (Default) - LastVersion=
RunningIncompat
Signal: 11
SourcePackage: firefox
StacktraceTop:
?? () from /usr/lib/
g_main_
?? () from /lib/x86_
g_main_
?? () from /usr/lib/
Title: firefox crashed with SIGSEGV in g_main_
UpgradeStatus: Upgraded to saucy on 2013-09-01 (18 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape video
dmi.bios.date: 07/01/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC1WW (2.21 )
dmi.board.name: 7743W73
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 7743W73
dmi.product.
dmi.sys.vendor: LENOVO
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1196700, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.