Binary package hint: xorg
Not sure if this is to be considered a Firefox or X bug. If I open a html file with some big font in it, like the one attached, as I start scrolling up-down and left-right around the page the X process start eating memory so fast that in few seconds the kernel starts OOM killing, or it pages so violently it takes ages to kill X even using Alt -SysRq -k. I've 3Gb of physical memory and gets filled in a matter of seconds. If you manage to kill firefox in time X does not release the memory.
I consider this a really serious problem, and do not know whether is an X or firefox problem. With chrome everything is ok.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic i686
Architecture: i386
DRM.card0.DVI.D.1:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 1400x1050
edid-base64: AP///////wAwriJAAAAAABoRAQOAHRV46m+VnFRMhyYhUFQAAAABAQEBAQEBAQEBAQEBAQEBMCp4IFEaEEAwcBMAH9cQAAAYJSN4IFEaEEAwcBMAH9cQAAAYAAAADwCQQzKQQygPAQAwZABVAAAA/gBMVEQxNDFFTjlCCiAgAP8=
DRM.card0.VGA.1:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
Date: Tue Mar 1 04:24:28 2011
DkmsStatus:
tp-smapi, 0.40, 2.6.35-23-generic, i686: installed
tp-smapi, 0.40, 2.6.35-24-generic, i686: installed
tp-smapi, 0.40, 2.6.35-25-generic, i686: installed
vboxhost, 4.0.4: added
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: LENOVO 1951A47
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-25-generic root=UUID=2b4896c4-f325-4833-97d8-5b7cb0d9355d ro quiet splash
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg crash
dmi.bios.date: 09/12/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ETE3WW (2.23 )
dmi.board.name: 1951A47
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn1951A47:pvrThinkPadT60:rvnLENOVO:rn1951A47:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 1951A47
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO
system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.35-25-generic
[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
Subsystem: Lenovo ThinkPad T60/R60 series [17aa:201a]
---
Architecture: i386
DistroCodename: natty
DistroRelease: Ubuntu 11.04
DistroVariant: ubuntu
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Package: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1
PackageArchitecture: i386
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Tags: natty running-unity ubuntu
Uname: Linux 2.6.38-8-generic i686
UnreportableReason: Please work this issue through technical support channels first.
UpgradeStatus: Upgraded to natty on 2011-05-14 (0 days ago)
UserGroups: adm admin cdrom dialout dip libvirtd lpadmin plugdev sambashare vboxusers
Hey valerio,
Thanks for your interest in Ubuntu.
Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?
If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.
If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.
If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.