[Ubuntu-x-swat] [Bug 1218839] Re: Xorg crashed with SIGABRT in compute_image_info()

2013-10-09 Thread Launchpad Bug Tracker
This bug was fixed in the package xserver-xorg-video-intel - 2:2.99.904-0ubuntu1 --- xserver-xorg-video-intel (2:2.99.904-0ubuntu1) saucy; urgency=low * Merge from unreleased debian git - new release candidate (LP: #1218839, #1157458, #1216252, #1232546) * xmir.patch:

[Ubuntu-x-swat] [Bug 1218839] Re: Xorg crashed with SIGABRT in compute_image_info()

2013-10-08 Thread Chris Wilson
I've found a source of memory corruption: commit 06a8ad9690590a605b1564012d062b98c60546a6 Author: Chris Wilson ch...@chris-wilson.co.uk Date: Mon Oct 7 23:21:38 2013 +0100 sna/trapezoids: Recompute num_threads to match range We need to be careful not to execute threads past the

[Ubuntu-x-swat] [Bug 1218839] Re: Xorg crashed with SIGABRT in compute_image_info()

2013-09-26 Thread Timo Aaltonen
** Package changed: xorg-server (Ubuntu) = xserver-xorg-video-intel (Ubuntu) ** Changed in: xserver-xorg-video-intel (Ubuntu) Importance: Medium = Critical -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu.

[Ubuntu-x-swat] [Bug 1218839] Re: Xorg crashed with SIGABRT in compute_image_info()

2013-09-26 Thread Chris Wilson
The stacktrace suggests memory corruption (image-common.transform is an invalid pointer, but if it exists it has to be a valid transform - therefore something far more wacky took place). Grabbing a profile of the high cpu loads is likely to give a clearer picture of what occurs after the

[Ubuntu-x-swat] [Bug 1218839] Re: Xorg crashed with SIGABRT in compute_image_info()

2013-09-09 Thread Maarten Lankhorst
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1218839 Title: Xorg crashed with SIGABRT in compute_image_info() To manage