Thomas Henn wrote: > Hi all, > > there is a memory corruption during destruction of the context. This > seems to be the same bug as reported here: > <http://sourceforge.net/mailarchive/forum.php?thread_name=16558747.post%40talk.nabble.com&forum_name=mesa3d-users> > > > > But I think it appears each time WMesaDestroyContext is called. I could > reproduce the problem with gears.exe and _heapchk(). Although I wasn't > able to track down the problem, uncommenting _mesa_free_context_data in > that function seems to be a workaround. > > Could anyone have a look at this?
I can't test on Windows, but perhaps you could narrow this down a bit. If you go into _mesa_free_context_data() in main/context.c, try putting #if 0 / #endif around various blocks of code. You might be able to determine which deallocation is at fault. My hunch is commenting out the _mesa_unreference_framebuffer() calls will "solve" the problem. If that's the case, wmesa_free_framebuffer() is probably the real issue. It looks like it frees the framebuffer object regardless of the reference count. -Brian ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
