opengl error with i830_vtbl.c:465: i830_emit_state: Assertion `0' failed.

[Eero Pajarre]

Binary package hint: libgl1-mesa-dri

this happens with my own OpenGL program on 8.10.
I have been porting the program from Windows and from
a more capable graphics card to Ubuntu and not so powerful
Intel graphics chip, so it is quite possible that my program still has
bugs in it. Still this failure is not proper way for OpenGL to behave.

I probably should go with this directly to Mesa people?

  Eero

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface [8086:2570] (rev 02)
     Subsystem: Hewlett-Packard Company Device [103c:12bc]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated Graphics Controller [8086:2572] (rev 02)
     Subsystem: Hewlett-Packard Company Device [103c:12bc]

[Eero Pajarre (epajarre)]

The reason for the program crash is that for some reason the distributed version has been
compiled with assertions active, and the code contains assert(0).

This assert is after the DRI code which sets up an an out of memory error message.
   if (ret) {
       if (count == 0) {
    count++;
    intel_batchbuffer_flush(intel->batch);
    goto again;
       } else {
    _mesa_error(ctx, GL_OUT_OF_MEMORY, "i830 emit state");
    assert(0);
       }
   }

I suspect that in this case the GL_OUT_OF_MEMORY condition would have been
more useful for me as an application developer. Maybe the library should be distributed
without the asserts compiled in?

[Bryce Harrington (bryce)]

Hi epajarre,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[Eero Pajarre (epajarre)]

Adding requested attachments.
The Xorg.0.log seems to indicate an "out of texture memory"
condition, which can be disappointing, but true.
(Still the OpenGL should return the corresponding error,
not abort)

[Eero Pajarre (epajarre)]

(got only one attachment per message ?)

[Geir Ove Myhr (gomyhr)]

Yes, the web interface currently only allows only one attachment per message. See bug 82652 for progress on this. The email interface allows you to upload many attachments at once by sending an email with a comment and attachments to <bugnr>@bugs.launchpad.net.

[Bryce Harrington (bryce)]

Indeed, it's asserting on the memory condition rather than returning an error code, so this is a legitimate problem. The particular function this occurs in, i830_emit_state() has a void return though, so it's not clear what should be done differently. However probably we should send this upstream for their comment.

[Jon Stumpf (jon-stumpf)]

Is there a workaround for this (e.g., disable desktop effects)?
Is there a timeframe to fix this issue?