Re: [Mesa3d-users] Heap Corruption?

[Brian P. <bri...@tu...>]

sdc395 wrote:
> 
> sdc395 wrote:
>> Hello list
>>
>> I appear to be suffering heap corruption caused by creating, applying,
>> deleting and then recreating a Mesa3D context within a Windows
>> application.
>>
>> To demonstrate, I've built the latest version of Mesa3D (7.0.3) using
>> Visual Studio 2005 and used the libraries with a sample application I
>> downloaded from  http://www.nullterminator.net/opengl32.html here .  I
>> moved the calls to EnableOpenGL() and DisableOpenGL() (see the sample
>> code) to reside within the rendering loop and BANG!
>>
>> I realise this is bad practice but surely it should work regardless.  I my
>> real application, I create and destroy contexts alongside CViews of the
>> application's model.  This works fine using Windows' own OpenGL
>> implementation but dies as soon as I switch to using Mesa3D.
>>
> Just thought I'd follow this up to let everyone know that things appear
> unchanged for 7.0.4 and 7.1.  I've spent as much time as I dare trying to
> pin the problem down but, since no one seems to be interested in fixing it
> (or even trying to reproduce it), we're simply going to have to abandon
> Mesa3D.  It's supposed to be our emergency rendering option but it's more
> trouble than it's worth.

You might get a better audience on the mesa3d-dev list.

Can you provide a stack trace or any other info from the crash?

Can you try a memory checker like Purify (or equivalent)?  You might be 
able to get a trial version of Purify.

You could also try a few things like disabling the rendering code in the 
loop to see if that's involved.

-Brian