Arch Linux

Malvineous

Member

From: Brisbane, Australia

Registered: 2011-02-03

Posts: 193

Website

OpenGL apps freeze on initial draw

Hi all,

I'm experiencing issues with OpenGL whereby when the app first draws to the screen it freezes - usually all I see is the window border, with whatever was on the screen before still visible inside the border.  The app will stay like this indefinitely, but if I switch to another desktop and back again the app will resume and the content will be drawn.

The apps usually continue to work until they are resized or moved, at which point they freeze again, and changing desktops brings them back to life.

Has anyone experienced this before?  I thought it was a bug in the OpenGL app I'm working on, but even the examples are doing this - e.g. if I copy and paste the code from example 9-1 in this guide (and compile it with "g++ -o gltest gltest.cpp -lGL -lGLU -lglut") the squares aren't drawn on the screen until I switch desktops first.

If I break this example in GDB while it is locked, here is where the freeze happens:

bt
#0  0x00007ffff6bdc9d7 in sched_yield () from /lib/libc.so.6
#1  0x00007ffff7b42b59 in ?? () from /usr/lib/libGL.so.1
#2  0x00007ffff5c38bd2 in ?? () from /usr/lib/libnvidia-glcore.so.270.41.06
#3  0x00007ffff5c151ec in ?? () from /usr/lib/libnvidia-glcore.so.270.41.06
#4  0x00007ffff5bf365e in ?? () from /usr/lib/libnvidia-glcore.so.270.41.06
#5  0x00007ffff5c36cf9 in ?? () from /usr/lib/libnvidia-glcore.so.270.41.06
#6  0x00007ffff5ba93d6 in ?? () from /usr/lib/libnvidia-glcore.so.270.41.06
#7  0x00007ffff5a09350 in ?? () from /usr/lib/libnvidia-glcore.so.270.41.06
#8  0x0000000000401260 in display () at gltest.cpp:54
#9  0x00007ffff7640d3d in fghcbDisplayWindow () from /usr/lib/libglut.so.3
#10 0x00007ffff76448a9 in fgEnumWindows () from /usr/lib/libglut.so.3
#11 0x00007ffff76411e1 in glutMainLoopEvent () from /usr/lib/libglut.so.3
#12 0x00007ffff7641b17 in glutMainLoop () from /usr/lib/libglut.so.3
#13 0x0000000000401534 in main (argc=2, argv=0x7fffffffe218) at gltest.cpp:106

I found an environment variable that prevents the nVidia driver from calling sched_yield() however the only change this has is that the CPU usage jumps to 100% during the freeze.

The driver is obviously waiting for *something* to happen, but I've no idea what!  Has anyone seen this problem before, or have any ideas what might be causing it?

I'm running Arch x86_64 with kernel 2.6.38 and nVidia drivers 270.41.06-1 and the Awesome window manager version 3.4.9.

Last edited by Malvineous (2011-05-15 11:05:09)