[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#531834: libgl1-mesa-dri: Assertion `intel->batch->ptr == intel->batch->map + intel->batch->offset' failed



On Thu, Jun  4, 2009 at 12:09:58 +0100, Philip Ashmore wrote:

> I'm experiencing OpenGL-related crashes on my laptop - sometimes an app will simply die for no apparent
> reason.
> I used valgrind to check what was happening and ran the "engine" screensaver included in xscreensaver-gl
> as a test
> 
>     valgrind -v --leak-check=full --show-reachable=yes /usr/lib/xscreensaver/engine 2>&1 | tee run.txt
> 
> When the app started I grabbed the lower-right-corner of the window with the mouse and resized
> "vigrously" until the app disappeared. Then I let go and move the mouse - kaboom! Assertion error.
> See attached dump file.


> engine: warning: only 4% idle over the last 11 secs (at 1.4 FPS)
> DRM_I830_BATCHBUFFER: -22
> engine: intel_context.c:733: UNLOCK_HARDWARE: Assertion `intel->batch->ptr == intel->batch->map + intel->batch->offset' failed.
> ==3560== 
> ==3560== Process terminating with default action of signal 6 (SIGABRT)
> ==3560==    at 0x67B8ED5: raise (in /lib/libc-2.7.so)
> ==3560==    by 0x67BA3F2: abort (in /lib/libc-2.7.so)
> ==3560==    by 0x67B1DC8: __assert_fail (in /lib/libc-2.7.so)
> ==3560==    by 0x826A07C: UNLOCK_HARDWARE (intel_context.c:733)
> ==3560==    by 0x826B24A: intel_batch_ioctl (intel_ioctl.c:161)
> ==3560==    by 0x8267228: intel_batchbuffer_flush (intel_batchbuffer.c:188)
> ==3560==    by 0x827C408: brw_try_draw_prims (brw_draw.c:361)
> ==3560==    by 0x827C8C5: brw_draw_prims (brw_draw.c:446)
> ==3560==    by 0x8323FF6: vbo_save_playback_vertex_list (vbo_save_draw.c:220)
> ==3560==    by 0x82B75D9: execute_list (dlist.c:5784)
> ==3560==    by 0x82B9DD9: _mesa_CallList (dlist.c:6872)
> ==3560==    by 0x404C91: (within /usr/lib/xscreensaver/engine)
> ==3560== 

Hi Philip,

is this assertion failure still reproducible with mesa 7.7 or 7.8?

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


Reply to: