Those are "object-oriented" and have some place to stash the string buffer. The only such place for al_get_current_directory() is in a global variable, which introduces problems with threads. Then we would need to make it thread-local, which introduces its own issues.

Just make a function that copies the string to your preferred location, and free Allegro's string immediately. You can make assumptions in your application that Allegro can't.

That problem seems to happen on some computers.. It should be known that there is no loop in the display creation code AFAIK. So whatever is happening is a driver or d3d bug.

So far we have no idea what causes it.

Well, the attached log does suggest some kind of loop. I added a bug report for it so we won't forget before the final 5.0, but hopefully we'll be able to fix it right away.

It's a D3D bug. It has to do with matching the best display format.

Hmm in that case I don't know

Ohh.. I noticed something quite wrong in your code.

Do not use & to combine flags. use |.

Please re try both of your examples!

Oh duh! Sorry and I'll try it again.

edit: Yea that seems to be the problem (same with the previous one, probably). Sorry for wasting everyone's time! (my excuse is I haven't used bit operations in a long time, but that's a rather lame excuse... "Oh, I haven't ridden a bike in four years! How will I remember?")

edit: Actually that really should have no effect. ALLEGRO_OPENGL & ALLEGRO_WINDOWED is 0. Would that not be a valid input? After all, it'd just default to the regular settings (or am I wrong?). In any case, I encountered a crash again after doing some other stuff, tried the code previously with the fix, and lo and behold it happens. So I guess I wasn't wasting anyone's time.

I haven't had it crash yet with OpenGL, just Direct3D in d3d_shutdown.

By Direct3D I mean when I do not set any flags (through al_set_new_display_flags).

When I use Direct3D it crashes (by using the code below) at the end of the program:

al_set_new_display_flags(0); /* Or just not calling it at all. */

And this does not crash at the end:

al_set_new_display_flags(ALLEGRO_OPENGL)

The example I am using is just this:

By default, this would use the Direct3D driver on Windows, or am I wrong?

I really don't mean to be a pain but I found a problem with getting display modes in OpenGL. The "height" member in ALLEGRO_DISPLAY_MODE is never set. I looked at the source and understand why the pixel format is not filled, so I ignore that for OpenGL contexts, but the height is important. Code is like so:

ALLEGRO_DISPLAY_MODE mode;
al_set_new_display_option(ALLEGRO_SAMPLE_BUFFERS, 1, ALLEGRO_SUGGEST);
al_set_new_display_option(ALLEGRO_SAMPLES, 16, ALLEGRO_SUGGEST);
al_set_new_display_option(ALLEGRO_STENCIL_SIZE, 8, ALLEGRO_SUGGEST);
al_get_display_mode(0, &mode)

printf("%d %d", mode.width, mode.height) /* Prints 640 0 (for example). */

I noticed that but assumed he was still using OpenGL after correcting that.

Aaron, if you're able to repeat this bug, could you please try adding a delay (Try Sleep(1000) on windows) after al_uninstall_sytem and before returning from main? I think it's a race condition. I was only able to reproduce it once though so I'm not sure.

Aaron, for the second bug about OpenGL display modes, try the patch attached to this post.

YW. What about the delay I suggested a couple posts above?