[i945gme] Moving pointer over Unity's launcher crashes X and causes Unity to reload

Bug #629814 reported by Vish
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
New
Undecided
Unassigned
xserver-xorg-video-intel (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

This happens very often in Unity session.

All i need to do is to move the pointer rapidly over the unity launcher and everything freezes for a couple of secs.
Then Unity reloads.
But i'm not booted out of the session. Only Unity re-loads

Attaching the gdb while this occured

---
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e83bb]
1: /usr/bin/X (0x8048000+0x5da8d) [0x80a5a8d]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xbd840c]
3: /usr/bin/X (FreeClientResources+0xed) [0x808f04d]
4: /usr/bin/X (FreeAllResources+0x60) [0x808f120]
5: /usr/bin/X (0x8048000+0x1a5e6) [0x80625e6]
6: /lib/libc.so.6 (__libc_start_main+0xe7) [0x58bce7]
7: /usr/bin/X (0x8048000+0x1a191) [0x8062191]
Segmentation fault at address 0x4

Caught signal 11 (Segmentation fault). Server aborting
---

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1024x600
 edid-base64: AP///////wAGr8ITAAAAAAESAQOAFAt4CuFFlVpXlCQZUFQAAAABAQEBAQEBAQEBAQEBAQEBfBUArkFYHiAYiDEAw3EAAAAYAAAADwAAAAAAAAAAAAAAAAAgAAAA/gBBVU8KICAgICAgICAgAAAA/gBCMDg5QVcwMSBWMyAKADc=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
Date: Fri Sep 3 20:31:21 2010
LiveMediaBuild: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Beta i386 (20100831.1)
MachineType: Acer AOA150
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname-netbook.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-intel
dmi.bios.date: 10/06/2008
dmi.bios.vendor: Acer
dmi.bios.version: v0.3308
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAcer:bvrv0.3308:bd10/06/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AOA150
dmi.product.version: 1
dmi.sys.vendor: Acer
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-19-generic

Revision history for this message
Vish (vish) wrote :
summary: - Moving pointer over Unity's launcher crashes X and causes WM to reload
+ Moving pointer over Unity's launcher crashes X and causes Unity to
+ reload
Vish (vish)
summary: - Moving pointer over Unity's launcher crashes X and causes Unity to
- reload
+ [i945gme] Moving pointer over Unity's launcher crashes X and causes
+ Unity to reload
Robert Hooker (sarvatt)
Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
description: updated
Revision history for this message
Vish (vish) wrote :

Ran debugging again, this time for both Xorg and mutter...
Looks like mutter just gets SIGKILL'd ...
Still confused though as to why i dont get logged out of the session.

Do let me know if i need to provide any other debugging

Revision history for this message
Vish (vish) wrote :
Revision history for this message
Albert Damen (albrt) wrote :

CurrentDmesg shows:

[12436.390414] Out of memory: kill process 29463 (mutter) score 157749 or a child
[12436.390430] Killed process 29463 (mutter) vsz:630996kB, anon-rss:13324kB, file-rss:16868kB

So mutter was killed because you ran out of memory. It looks like mutter is using a lot of RAM.
You seem to have 1GB of RAM and no swap space enabled. I suggest you first create some swap space. That should prevent the crash and give you time to find out what is using all your memory.

Revision history for this message
Vish (vish) wrote :

This might be related to Bug #604777 [massive memory leak when hovering over the quicklists] , but not marking this as a dup yet .

We can probably wait for Bug #604777 to be fixed and check again if there are any X crashes..

Revision history for this message
Vish (vish) wrote :

This might be related to Bug #604777 [massive memory leak when hovering over the quicklists] , but not marking this as a dup yet .

We can probably wait for Bug #604777 to be fixed and check again if there are any X problems..

Bryce Harrington (bryce)
tags: added: crash
Revision history for this message
Vish (vish) wrote :

The memory leak issue fixed this bug as well , so marking it as a dup of Bug #604777

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.