OpenGL GLUT Renders only One Frame

Question

I wrote a completely trivial program - it simply opens a window and renders a black screen. When I call glutMainLoop() it renders a single frame then hangs. Sampling gives me these results
Sampling process 1950 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling output (pid 1950) every 1 millisecond
Call graph:
2162 Thread_2503
2162 start
2162 main
2162 glutMainLoop
2162 -[GLUTApplication run]
2162 -[GLUTApplication _runMainLoopUntilDate:autoreleasePool:]
2162 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
2162 _DPSNextEvent
2162 BlockUntilNextEventMatchingListInMode
2162 ReceiveNextEventCommon
2162 RunCurrentEventLoopInMode
2162 CFRunLoopRunInMode
2162 CFRunLoopRunSpecific
2162 mach_msg
2162 machmsgtrap
2162 machmsgtrap
2162 Thread_2603
2162 thread_start
2162 pthreadstart
2162 glvmDoWork
2162 pthreadcondwait$UNIX2003
2162 _semwaitsignal
2162 _semwaitsignal
Total number in stack (recursive counted multiple, when >=5):
Sort by top of stack, same collapsed (when >= 5):
_semwaitsignal 2162
machmsgtrap 2162
Sample analysis of process 1950 written to file /dev/stdout
Any help will be greatly appreciated
The completely trivial code:
#include <stdio.h>
#include <stdlib.h>
#include <GLUT/glut.h>
/* function prototypes */
/* opengl std */
void display();
void init();
unsigned long frames=0;
int main(int argc, char **argv){
glutInit(&argc, argv);
glutInitDisplayMode(GLUT_SINGLE | GLUT_RGB);
glutInitWindowSize(500, 500);
glutInitWindowPosition(100, 100);
glutCreateWindow("ZOMG!!!");
init();
glutDisplayFunc(display);
glutMainLoop();
return 0;
void display(){
printf("Frames[%lu]
", frames++);
glClear(GLCOLOR_BUFFERBIT);
glLoadIdentity();
glFlush();
printf("frame drawn
void init(){
glClearColor(0.0, 0.0, 0.0, 0.0);
glShadeModel(GL_SMOOTH);
Message was edited by: rabidgnome
Message was edited by: rabidgnome

Answer 1

I wouldn't say Sg is a badly compromised program ... if one takes a car and tries to make it do the work of a truck, well ... one will be unhappy with the car, but is it really the fault of the makers of the car?
Speedgrade has it's glitches, and no one on the planet can tell you more about them than the guys that created it or those that are working it behind the scenes. But Speedgrade is designed to be a grading program ... not an NLE or an encoding program. It has those functions simply so that for some who say just want to do quick dailies probably doing quick & dirty grading of un-trimmed "clips" just to get something out for directors to see if what they shot will work. In my experience, for that use you need to know exactly how it needs setting, and have your presets stored.
The whole idea of this software is to be part of a group ... each program specialized into one set of problems, rather than each trying to be an equal Swiss-Army knife. And in use, it works quite well (for most of us most of the time) though there are a few glitches. Such as say, key-framed masks that at times can be problematic. Be that as it is, use the program for what it is designed for. Within that, it can be pretty awesome.