[Bug 81215] [IVB/HSW/BYT/BDW Bisected]Show backtrace when running Synmark2 v6.0 OglTexMem512

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Jul 22 01:16:27 PDT 2014


https://bugs.freedesktop.org/show_bug.cgi?id=81215

--- Comment #28 from Chris Wilson <chris at chris-wilson.co.uk> ---
==8677== Invalid read of size 8
==8677==    at 0x5204E3: present_destroy_window (present_screen.c:93)
==8677==    by 0x4D9C70: compDestroyWindow (compwindow.c:608)
==8677==    by 0x4FBE11: DbeDestroyWindow (dbe.c:1318)
==8677==    by 0x4623D6: FreeWindowResources (window.c:910)
==8677==    by 0x464F97: DeleteWindow (window.c:978)
==8677==    by 0x45B2D1: doFreeResource (resource.c:873)
==8677==    by 0x45BD92: FreeResource (resource.c:903)
==8677==    by 0x433FE6: ProcDestroyWindow (dispatch.c:719)
==8677==    by 0x439186: Dispatch (dispatch.c:432)
==8677==    by 0x43CF49: dix_main (main.c:296)
==8677==    by 0x7197DE4: (below main) (libc-start.c:260)
==8677==  Address 0xea82eb8 is 40 bytes inside a block of size 168 free'd
==8677==    at 0x4C2B60C: free (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8677==    by 0x5204A2: present_destroy_window (present_screen.c:79)
==8677==    by 0x4D9C70: compDestroyWindow (compwindow.c:608)
==8677==    by 0x4FBE11: DbeDestroyWindow (dbe.c:1318)
==8677==    by 0x4623D6: FreeWindowResources (window.c:910)
==8677==    by 0x464F97: DeleteWindow (window.c:978)
==8677==    by 0x45B2D1: doFreeResource (resource.c:873)
==8677==    by 0x45BD92: FreeResource (resource.c:903)
==8677==    by 0x433FE6: ProcDestroyWindow (dispatch.c:719)
==8677==    by 0x439186: Dispatch (dispatch.c:432)
==8677==    by 0x43CF49: dix_main (main.c:296)
==8677==    by 0x7197DE4: (below main) (libc-start.c:260)

which is one of the bugs I reported to Keith earlier.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140722/3ed7adfe/attachment.html>


More information about the intel-gfx-bugs mailing list