Raring beta screen greying out and getting unresponsive

Bug #1166186 reported by jerrylamos
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Running Firefox on Raring beta 2 getting frequent periods of screen greying out and won't respond, recovers, then greys out again. I did get this message once:

(process:5599): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed

Maybe this is a linux bug instead? How do I tell what process 5599 is? It's not showing up on "top".

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: firefox 20.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jerry 1511 F.... pulseaudio
BuildID: 20130404201520
Channel: Unavailable
Date: Mon Apr 8 08:51:50 2013
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-04-02 (5 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
IpRoute:
 default via 192.168.0.1 dev wlan0 proto static
 169.254.0.0/16 dev wlan0 scope link metric 1000
 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.7 metric 9
MarkForUpload: True
PrefSources: prefs.js
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=20.0/20130404201520 (In use)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
 totem-mozilla 3.6.3-0ubuntu4
 rhythmbox-mozilla 2.98-0ubuntu3
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/16/2010
dmi.bios.vendor: Acer
dmi.bios.version: V3.12(DDR3)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE02_PT
dmi.board.vendor: Acer
dmi.board.version: V3.12(DDR3)
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V3.12(DDR3)
dmi.modalias: dmi:bvnAcer:bvrV3.12(DDR3):bd12/16/2010:svnAcer:pnAOD255E:pvrV3.12(DDR3):rvnAcer:rnJE02_PT:rvrV3.12(DDR3):cvnAcer:ct10:cvrV3.12(DDR3):
dmi.product.name: AOD255E
dmi.product.version: V3.12(DDR3)
dmi.sys.vendor: Acer

Revision history for this message
jerrylamos (jerrylamos) wrote :
Revision history for this message
jerrylamos (jerrylamos) wrote :

Firefox is showing up to 75% CPU (dual processor) while working on this bug and not doing anything with firefox other than sitting there with 6 tabs, highlighted tab is BUG #1166186 ( this one).

I've been running Raring since early apt/sources.list days and haven't seen anything like this.

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.04
DISTRIB_CODENAME=raring
DISTRIB_DESCRIPTION="Ubuntu Raring Ringtail (development branch)"
Linux Aspire1 3.8.0-16-generic #26-Ubuntu SMP Mon Apr 1 19:52:57 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Updated as of today 8 April. Very slow with raring stuttering along to enter this bug comment.

Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Presumably this problem was a one time occurrence and/or is no longer an issue? Can the bug report now be closed? If we do not hear from you the bug report will close itself in approximately 60 days time.

Thank you again for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

Changed in firefox (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]

Changed in firefox (Ubuntu):
status: Incomplete → Expired
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.