[Mesa-dev] [Bug 102038] assertion failure in update_framebuffer_size

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Aug 4 15:33:43 UTC 2017


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

            Bug ID: 102038
           Summary: assertion failure in update_framebuffer_size
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/swr
          Assignee: mesa-dev at lists.freedesktop.org
          Reporter: brad.king at kitware.com
        QA Contact: mesa-dev at lists.freedesktop.org

Created attachment 133247
  --> https://bugs.freedesktop.org/attachment.cgi?id=133247&action=edit
apitrace of test that crashes

Since commit 6839d33699 (st/mesa: fix handling of NumSamples=1 (v2),
2017-08-01) many of VTK's tests crash with Mesa with an assertion failure. 
I've attached an apitrace of one of the tests.

The test aborts with an assertion failure:

```
state_tracker/st_atom_framebuffer.c:62: update_framebuffer_size: Assertion
`surface' failed.
```

The backtrace in gdb is

```
#0  __GI_raise (sig=sig at entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007ffff7a6e3fa in __GI_abort () at abort.c:89
#2  0x00007ffff7a65e37 in __assert_fail_base (fmt=<optimized out>, 
    assertion=assertion at entry=0x7fffec7516a4 "surface", 
    file=file at entry=0x7fffec751680 "state_tracker/st_atom_framebuffer.c", 
    line=line at entry=62, 
    function=function at entry=0x7fffec7517a0 <__PRETTY_FUNCTION__.39021>
"update_framebuffer_size") at assert.c:92
#3  0x00007ffff7a65ee2 in __GI___assert_fail (
    assertion=0x7fffec7516a4 "surface", 
    file=0x7fffec751680 "state_tracker/st_atom_framebuffer.c", line=62, 
    function=0x7fffec7517a0 <__PRETTY_FUNCTION__.39021>
"update_framebuffer_size") at assert.c:101
#4  0x00007fffec336bad in update_framebuffer_size (framebuffer=0x7fffffffce70, 
    surface=0x0) at state_tracker/st_atom_framebuffer.c:62
#5  0x00007fffec336f3e in st_update_framebuffer_state (st=0x555555ae3b90)
    at state_tracker/st_atom_framebuffer.c:181
#6  0x00007fffec33538c in st_validate_state (st=0x555555ae3b90, 
    pipeline=ST_PIPELINE_CLEAR) at state_tracker/st_atom.c:251
#7  0x00007fffec3428ea in st_Clear (ctx=0x555555abeb30, mask=18)
    at state_tracker/st_cb_clear.c:411
#8  0x00007fffec0a2b4a in clear (no_error=false, mask=16640,
ctx=0x555555abeb30)
    at main/clear.c:221
#9  _mesa_Clear (mask=16640) at main/clear.c:242
...(vtk code)...
```

For reference, I'm building Mesa as follows:

    ./autogen.sh \
      --prefix="$prefix" \
      --enable-debug \
      --disable-dri \
      --disable-egl \
      --disable-gbm \
      --disable-gles1 \
      --disable-gles2 \
      --disable-shared-glapi \
      --with-platforms=x11 \
      --enable-glx=gallium-xlib \
      --enable-gallium-osmesa \
      --with-gallium-drivers=swrast \
      --enable-gallium-llvm=yes \
        LLVM_CONFIG=/usr/bin/llvm-config-3.8 \
      --enable-llvm-shared-libs \
      --with-gl-lib-name=MesaGL \
      --with-osmesa-lib-name=MesaOSMesa

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20170804/98468268/attachment.html>


More information about the mesa-dev mailing list