Random Linux Crashes - X Error failed request: BadWindow
 

MacBook Pro on ubuntu (Edgy) with drivers all installed.

NPC Code:

---

Activating the OpenGL display device (1)...

Setting screen mode to 1440x850x32 (w)...

OpenGL Attributes:

  DoubleBuffer: 1

  BufferSize: 32, DepthSize: 24, StencilSize: 0

  Red: 8, Green: 8, Blue: 8, Alpha: 8

  Accum Red: 0, Green: 0, Blue: 0, Alpha: 0

OpenGL driver information:

  Vendor: ATI Technologies Inc.

  Renderer: ATI Mobility Radeon X1600 Generic

  Version: 2.0.6065 (8.29.6)

OpenGL Init: Enabled Extensions

  ARB_multitexture (Max Texture Units: 8)

  EXT_compiled_vertex_array

  EXT_texture_env_combine

  EXT_packed_pixels

  EXT_fog_coord

  ARB_texture_rectangle

  ARB_texture_compression

  EXT_texture_compression_s3tc

  (ARB|EXT)_texture_env_add

  EXT_texture_filter_anisotropic (Max anisotropy: 16.000000)

  EXT_stencil_wrap

  ARB_vertex_blend

OpenGL Init: Disabled Extensions

  EXT_paletted_texture

  NV_vertex_array_range

  3DFX_texture_compression_FXT1

  WGL_EXT_swap_control

  EXT_stencil_two_side

  NV_depth_clamp

  EXT_depth_bounds_test

  NPatch tessellation

  

Graal has been activated!



[...]



File download: relic_wheat4.png (size: 897) done

File download: relic_wheat2.png (size: 1035) done

File download: relic_wheat1.png (size: 1028) done

% X Error of failed request:  BadWindow (invalid Window parameter)

  Major opcode of failed request:  20 (X_GetProperty)

  Resource id in failed request:  0xa3cf0c

  Serial number of failed request:  36

  Current serial number in output stream:  36

---

Randomly crashes. ( Or -- I just didn't find out what crashed it! )

Direct Rendering works...

Nothing significant happens in the duration thereof.

It seems to be a bug of recent x-servers (xorg), sometimes moving or resizing some window is killing opengl applications. Can't do something against that since it's done by the x-server and is killing the application without a notice, but I will try to find some more information about it since its annoying like hell.

Hrm -- I've been trying to solve this too...

I had beryl-manager on at the time of the crashes without XGL on. ( I closed it because direct-rendering didn't work as effectively while it was opened, I had to DISPLAY=:0 graal to have it ). When I removed the beryl-manager from the session, it seems to have fixed the problem. I don't know why it was doing it: It was pretty inactive as application.

Bah! Still crashes... But at a MUCH lesser frequency ( without beryl-manager )

Novo, what window manager are you using? I've had this bad window position error a lot with KDE, but not at all with WindowMaker or Gnome.

According to Stefan, it's not the windows manager that actually breaks it -- It's the recent update on the X-Server -- Both Gnome and KDE are based on this.

I suppose some windows managers fall on the bug more often though ( Beryl probably crashed so much more due to it being enhanced graphically, and uses a lot more exploitation in the system )

Okay. I'm going to upgrade to the latest X.org server (I was running a slightly older version I'm now upgrading to xorg-x11-server-7.2-56.1.i586 on SUSE 10.1) and see how if it makes any difference in those crashes.

Okay. I upgraded my X.org server and now I get a segmentation fault when opening Graal. Just like I did in this thread. So Stefan, if you are wondering what's causing segmentation faults in Intel graphics accelerators, it's most definitely the newest version of X.org.

But glxinfo and other opengl programs still work?

Yeah, they work great. glxgears gets an awesome framerate and 3D games work too.

Hmmm I can only imagine that there is some special OpenGL command not supported. When its crashing at startup, you still get a ~/.graal/graal4/console.log ?

About the random linux crashes, I have reduced the problem by not redrawing the window when some special events occur, so the next Graal version should work a little bit better.

Ok fixed it. It was quite hard to find because Xerrors are normally not printed when they are happening, so we had to set the XServer to synchronized mode.