You might try BoundsChecker ( Numega Dev Studio ), otherwise, debug the whole 10 times until it crashes :)

Memory Manager Tool

As a frequent abuser of dynamic memory allocations/deallocation I find this memory tracker code extremely usefull. Conceptually quite simple (all it does is replace new/delete/malloc/free etc.) it'll track any memory leaks, and even more usefull - will catch boundary over-runs (which 9 times out of 10 are what catch me out, and are often the cause of some really nasty and random program crashes).

Maybe that'll prove usefull in tracking down your bug. And even if it doesn't, its still a nice bit of code for development debuging (with the added advantage of being free! - something which BoundsChecker is most definatly not!)

Ben

The con with this tip is that it doesn't detect memory leaks on the driver side, just leaks on the application side (well, that's still a good thing to remove leaks on the app side!).

Quote: Original post by vincoof
that's still a good thing to remove leaks on the app side!

I would say it's the first thing to do. While removing leaks in your app, you can sometimes find 'leaks' in opengl (I know I did :)).