Author Topic: Xorg crashes  (Read 521 times)

BarryK

  • Administrator
  • Jr. Member
  • *****
  • Posts: 72
    • View Profile
Xorg crashes
« on: October 09, 2018, 04:05:39 AM »
Xorg periodically crashes, running Easy on my midi-tower PC. Intel hardware, using the Xorg 'modesetting' driver. The error log includes this:

"glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage"

Googled, found others have same experience, mostly in 2018. It seems to be due to loading of /usr/lib/xorg/modules/libglamoregl.so

Here is another report;

https://bbs.archlinux.org/viewtopic.php?id=212335

This problem started a few months ago, after I had recompiled in OpenEmbedded, with updated Xorg packages. ...the downside of upgrading!

I have removed that module, X still works, but GL is now software rendering.

nevarmaor

  • Newbie
  • *
  • Posts: 24
    • View Profile
Re: Xorg crashes
« Reply #1 on: October 10, 2018, 04:39:05 PM »
I had noticed that modesetting stopped working for me a few versions ago, probably right about the recompile time (0.9.2 maybe?). Any time it defaults to modesetting I was only getting a blinking cursor in the top left corner. Reboot to commandline and run xorgwizard to set to intel fixes it. Never got a desktop in modesetting though.

scsijon

  • Newbie
  • *
  • Posts: 48
    • View Profile
Re: Xorg crashes
« Reply #2 on: October 12, 2018, 11:19:50 PM »
Problem is that any function can add this message and it usually origonates from another program.

"glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage" is just the pass on message source.

For instance, Mesa, Evolution, OpenGl and the xorg-server itself are all known to have caused it, a lot of responsable thoughts seem to feed back to mesa though although the xorg-server (especially 1.18) is also blamed.

Have a look at the answer in https://stackoverflow.com/questions/34204537/how-to-handle-gl-out-of-memory-error-during-glbufferdata, it will give you an idea of the complexity to find the source.

And from OpenGL itself is this, https://www.opengl.org/discussion_boards/showthread.php/198564-Where-is-OUT-OF-MEMORY-when-allocate-textures, which clearly states the problem.