Created attachment 59517 [details] captured backtrace While working with eog ('the eye of gnome') suddenly X crashed. The crash appeared to happen at the exact moment of a click of the main eog-window, however I've been clicking that window for some time before and after the crash without adverse effects. I've attached the backtrace that was captured. My hardware is a Dell XPS 15 (L502x) laptop with: 00:02.0 VGA compatible controller: Intel Corporation Device 0116 (rev 09) [ 13.803] (II) intel(0): Integrated Graphics Chipset: Intel(R) Sandybridge Mobile (GT2) Running xf86-video-intel from git, commit 98ad4c3cd8647ba3ec90fb45157773c8e85e886c
That crash looks pretty inexplicable. The pointers are all valid, the indices are all within range... Meh.
Retitling as an expected SIGSEGV is unexpected.
Created attachment 59670 [details] captured backtrace 2 I just hit another SIGSEGV, which although not quite identical might be related as it also passes through tor_inplace: tor_inplace() calling fill_buckets() (please see attachment). This happened as I was watching some youtube videos, just as I clicked on the youtube searchbar. Intel driver is/was at commit b790ba2ec9ead51227d85fc8630bc7505eb7d7b3 .
That segfault is still collateral damage. Can you try reproducing with commit 2e4da00e3e03b873f5cad0cc5b1f6cc791852ca5 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Apr 9 10:42:18 2012 +0100 sna/traps: Assert that the inplace row is contained before writing References: https://bugs.freedesktop.org/show_bug.cgi?id=48332 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
commit 7f0bede3e7e3f92a637d1c886304b16afc0e34f2 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Apr 9 10:48:08 2012 +0100 sna/traps: Use a temporary variable for the write pointer To avoid accumulating the write offset for wide spans, we need to reset the destination pointer between spans. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=48332 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.