Catalyst 10.8/10.9 Heap Corruption

Discussion created by techraven on Oct 22, 2010
Latest reply on Nov 2, 2010 by techraven
Corruption when 10.8/10.9 is installed


I have a fairly large application that uses OpenGL, when the Catalyst 10.8 or 10.9 drivers are installed, errors like this occur.

I'll get these errors immediately after a glDrawElements or glColor3ub call. I've ran the application through several profilers and cannot track down any internal memory corruption. Also the heap it appears to be reporting corrupted is very odd.. 

If I go back to Catalyst 10.7 the problem goes away and everything runs fine. Any ideas as to what could be going on? Is there something new in the 10.8/10.9's that needs to be initialized that didn't need to be in 10.7? Is there some way I can begin to track this down?

HEAP[xxxxxx.exe]: Heap block at 0B03F288 modified at 0B03F2A3 past requested size of 13

Windows has triggered a breakpoint in xxxxxx.exe

0x0B03F288  bf 2a 53 61 d9 2f 0e 25 67 6c 5f 43 6c 69 70 44 69 73 74 61 6e 63 65 5b 2d 32 30 5d 00 ab ab ab  ¿*SaÙ/.%gl_ClipDistance[-20].«««

0x0B03F2A8  ab ab ab fe ee fe ee fe ee fe ee fe ee fe ee fe 00 00 00 00 00 00 00 00 92 2a 53 4c da 2f 0e 1c  «««þîþîþîþîþîþîþ........’*SLÚ/..