[Bug 85456] New: Segfault on glClear when running in fullscreen mode on GNOME
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Oct 25 13:50:14 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=85456
Bug ID: 85456
Summary: Segfault on glClear when running in fullscreen mode on
GNOME
Product: Mesa
Version: 10.2
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/i965
Assignee: idr at freedesktop.org
Reporter: fintelia at gmail.com
QA Contact: intel-3d-bugs at lists.freedesktop.org
When I run MPV in fullscreen mode it sometimes crashes with the following
output:
Failed to open BO for returned DRI2 buffer (1366x768, dri2 back buffer, named
29).
This is likely a bug in the X Server that will lead to a crash soon.
Segmentation fault (core dumped)
On occasion, it will crash GNOME as well ("Oh, no! Something has gone wrong.
problem has occured and the system can't recover. All extensions have been
disabled as a precaution. [Log Out]") The issue has already been described on
their bug tracker here: https://github.com/mpv-player/mpv/issues/1177. However,
it isn't actually just limited to this one program, I've encountered the same
thing in my own GLX/OpenGL code whenever I enable _NET_WM_STATE_FULLSCREEN.
I'm running Debian Jessie with Mesa 10.2.8 on an Intel i5-3230M CPU.
GDB Backtrace
--------------
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f86de1a9892 in brw_blorp_mip_info::set (this=0x7f86df026b38,
mt=0x0, level=0, layer=0)
at ../../../../../../../src/mesa/drivers/dri/i965/brw_blorp.cpp:71
71 ../../../../../../../src/mesa/drivers/dri/i965/brw_blorp.cpp: No such
file or directory.
(gdb) bt
#0 0x00007f86de1a9892 in brw_blorp_mip_info::set (this=0x7f86df026b38,
mt=0x0, level=0, layer=0)
at ../../../../../../../src/mesa/drivers/dri/i965/brw_blorp.cpp:71
#1 0x00007f86de1a9903 in brw_blorp_surface_info::set (
this=this at entry=0x7f86df026b38, brw=brw at entry=0x7f86d87de948, mt=0x0,
level=<optimized out>, layer=layer at entry=0,
is_render_target=is_render_target at entry=true)
at ../../../../../../../src/mesa/drivers/dri/i965/brw_blorp.cpp:83
#2 0x00007f86de1b5fb5 in brw_blorp_clear_params::brw_blorp_clear_params (
this=0x7f86df026ac0, brw=0x7f86d87de948, fb=0x7f86d85ee7c0,
rb=0x7f86d85eecd0,
color_mask=0x7f86d87e0130 '\377' <repeats 32 times>, "\005\004",
partial_clear=<optimized out>, layer=0)
at ../../../../../../../src/mesa/drivers/dri/i965/brw_blorp_clear.cpp:191
#3 0x00007f86de1b69d4 in do_single_blorp_clear (brw=0x7f86d87de948, fb=0x0,
fb at entry=0x7f86d85ee7c0, rb=0x0, rb at entry=0x7f86d85eecd0, buf=buf at entry=0,
partial_clear=partial_clear at entry=false, layer=1)
at ../../../../../../../src/mesa/drivers/dri/i965/brw_blorp_clear.cpp:505
#4 0x00007f86de1b6d3f in brw_blorp_clear_color (brw=brw at entry=0x7f86d87de948,
fb=fb at entry=0x7f86d85ee7c0, mask=mask at entry=2,
partial_clear=partial_clear at entry=false)
at ../../../../../../../src/mesa/drivers/dri/i965/brw_blorp_clear.cpp:601
#5 0x00007f86de1b8368 in brw_clear (ctx=0x7f86d87de948, mask=2)
---Type <return> to continue, or q <return> to quit---
at ../../../../../../../src/mesa/drivers/dri/i965/brw_clear.c:247
#6 0x00000000004a1426 in gl_video_render_frame (p=0x7f86d85f1d50)
at ../video/out/gl_video.c:1614
#7 0x00000000004a6104 in draw_image (vo=<optimized out>, mpi=0x17cb1d0)
at ../video/out/vo_opengl.c:167
#8 0x00000000004a42e1 in render_frame (vo=0x13a0f40) at ../video/out/vo.c:582
#9 vo_thread (ptr=0x13a0f40) at ../video/out/vo.c:682
#10 0x00007f86eb5950a4 in start_thread (arg=0x7f86df027700)
at pthread_create.c:309
#11 0x00007f86eb2cac2d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
(gdb) f 6
#6 0x00000000004a1426 in gl_video_render_frame (p=0x7f86d85f1d50)
at ../video/out/gl_video.c:1614
1614 gl->Clear(GL_COLOR_BUFFER_BIT);
--
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-3d-bugs/attachments/20141025/e9de52c6/attachment.html>
More information about the intel-3d-bugs
mailing list