[i965gm] 10.10 gem_objects are not released properly and generate memory overload

Bug #658746 reported by Walabom
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

While using my ubuntu, I realize my swap memory is progressivelly increasing.
I check GEM object size and find an increase :
gsi@mal-gsi:~$ cat /sys/kernel/debug/dri/0/gem_objects | grep 'object bytes'
309133312 object bytes

gsi@mal-gsi:~$ cat /sys/kernel/debug/dri/0/gem_objects | grep 'object bytes'
1232235864 object bytes

Until the number becomes negative and after the system freeze.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
DRM.card0.DVI.D.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1280x800
 edid-base64:
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
Date: Mon Oct 11 23:30:22 2010
DkmsStatus:
 vboxnetflt, 3.2.8: added
 vboxnetadp, 3.2.8: added
 vboxdrv, 3.2.8: added
MachineType: FUJITSU SIEMENS LIFEBOOK S7210
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   product info: "O2Micro", "SmartCardBus Reader", "V1.0", ""
   manfid: 0xffff, 0x0001
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   5.0V 16-bit PC Card
   Subdevice 0 (function 0) [unbound]
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=343f1837-eee7-45e4-8f24-9e9d050b05d6 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.utf8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-intel
dmi.bios.date: 08/20/2008
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.09
dmi.board.name: FJNB1DB
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: S7210
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.09:bd08/20/2008:svnFUJITSUSIEMENS:pnLIFEBOOKS7210:pvr:rvnFUJITSU:rnFJNB1DB:rvr:cvnFUJITSUSIEMENS:ct10:cvrS7210:
dmi.product.name: LIFEBOOK S7210
dmi.sys.vendor: FUJITSU SIEMENS
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-22-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Fujitsu Limited. Device [10cf:13f8]

Revision history for this message
Walabom (greg-sitbon) wrote :
Revision history for this message
Walabom (greg-sitbon) wrote :

hello,
after changing my theme from ubuntu sunrise to another, I don't have no more no memory leak!!!
freedom after so long!!!

Revision history for this message
Walabom (greg-sitbon) wrote :

this bug can be close

Revision history for this message
Miron Cuperman (devrandom) wrote :

I am affected by the same bug. This can be reproduced by changing the desktop background.

Revision history for this message
Miron Cuperman (devrandom) wrote :

I am able to reproduce this consistently on maverick. xorg virtual memory increases by 8MB every time I change the desktop background. xrestop is stable.

Running the intel driver, compiz, nautilus.

Linux mimiv 2.6.35-23-generic #41-Ubuntu SMP Wed Nov 24 10:18:49 UTC 2010 i686 GNU/Linux

ii xserver-xorg-video-intel 2:2.12.0-1ubuntu5.1
ii xorg 1:7.5+6ubuntu3 X.Org X Window System
ii xserver-xorg 1:7.5+6ubuntu3 the X.Org X server
ii xserver-xorg-core 2:1.9.0-0ubuntu7 Xorg X server - core server

Let me know what other information I can provide.

Revision history for this message
andrjas (andrjas) wrote :

I also have a problem with the gemleak. I'm using Kubuntu 10.10 x64 with intel graphics.
I've already tried the x-swat and xorg-edgers drivers. They have the same problem as the "original" one.

bugbot (bugbot)
description: updated
Revision history for this message
bugbot (bugbot) wrote :

Hey Walabom,

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.

bugbot (bugbot)
Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Incomplete
bugbot (bugbot)
summary: - 10.10 gem_objects are not released properly and generate memory overload
+ [i965gm] 10.10 gem_objects are not released properly and generate memory
+ overload
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in xserver-xorg-video-intel (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.