GL - what can cause this error?

I get an "Unhandled Memory Exception" error on calling End.

I've tried freeing all assets, sound channels, tLists etc and it makes no difference at all.

Everything works fine in DX. but under GL, I get the above error here (glgraphics.bmx):

	Method Close()
		If Not _context Return
		<b>bbGLGraphicsClose( _context )</b>
		_context=0
	End Method

I've tried setting up a basic program to create a graphics object in GL and then ending it, and that seems to work OK, so I guess its something I'm doing somewhere but I don't know what.

Any ideas what can cause this error? I'm at a loss.

You're going behind the scenes so who knows. Why not just call EndGraphics()?

No I'm not - I'm using 'End'! Its hardly low-level stuff.

The debugger is pointing me to glgraphics Close method.

I've already tried EndGraphics but I still get the same error.

No, what he's saying is that bbGLgraphicsClose is the one that is flaggin the exception with the debugger. Thats not his code, its from the BB source (i think).

Sounds like a BMX bug. What happens in release mode?

Correct - its from glgraphics.bmx. I did say that in my first post. :)

In release mode my game just hangs.

What are you exactly doing as you say that a basic sample does not have this error? Do you use extension modules like indiepaths or leadwerks AA addition?

do you do anything else that is not part of the default commandset of Max2D?

Sorry for reanimating old threads, but this is EXACTLY the error I'm getting since a few days in my app and it drives me crazy. As I can see I do nothing special and Under-the-hood stuff and it's seems to be a problem with GLMax2DDriver (or cards' OpenGL driver).

This error is somewhat random. On my home machine (ATI Radeon 1950 Pro) it occurs very rarely, about every 20. or 30. run. At work (Intel onboard) it occurs very often, aprox. each 2. run. Both machines running on XP Pro.

Could it be something with VRAM swapping? My app loads a lot of images.

Update your drivers to a WHQL certified version which is new. That should fix it.

With intel onboard you can be happy that OpenGL works at all because its Microsoft OpenGL 1.1 emulation (on GMA 900 at least)

It would be helpful if anyone (maybe from BRL) can say what things can raise this error and what not. Is it only memory hickup that can raise an unnamed MAV? I'm going through the BRL sources today and see what Endgraphics does and what may fail.