Here's a modified version of one of the DWT opengl snippets that reproduces the crash for me. About 1 in 10-15 runs this will crash (seems to be inside the GL driver) soon after startup with the error:
""" dwt.DWTException.DWTException: Failed to execute runnable object.Exception: Access Violation """ Can anyone else reproduce this (particularly Vista users)? I'd be happy to send the exe to anyone who would like to try it off list. But it's a 3MB exe (compresses to about .7 MB). --bb On Sun, Jan 18, 2009 at 11:35 PM, Sergey Kovrov <[email protected]> wrote: > On 1/18/2009 5:51 AM, Bill Baxter wrote: >> >> So far haven't been able to isolate it. >> I updated another program that displays meshes with similar code and >> it works fine. >> So sounds like some kind of memory problem in my code to me too. Or >> possibly passing a bad pointer to GL somewhere. I have glGetError's >> sprinkled all over my code and get no errors from that. But GL >> doesn't know if you pass it a bad pointer. >> >> I remember one problem I had long ago when I called glGetIntegerv for >> something, thinking it returned 1 value when it actually returned two. >> Seems likely it could be something similar here. >> >> --bb > > You could check if you have "wild" Client State somewhere ("wild" like in > "wild pointers"). It is easy to forget to call glDisableClientState for some > of GL_..._ARRAY capability when it no longer needed. And in such case error > might manifest it self in an unusual way, just like in case of generic > dangling pointers. > > -- serg. >
Snippet174.d
Description: Binary data
