Dangling pointers, NOT!


#1

Argh, after rebuilding my projects, all of a sudden and for no apparent reason I get assertions from Juce regarding dangling pointers!
Particularly, dangling pointer in File, i.e when I delete of of those, I appear to have deleted it already. (I haven’t!)

There is no apparent reason for it and the code has worked fine for years. I must have touched something.

Can someone give me a tip of what I could have messed with?
Latest tip, Windows, vs2012


#2

Just in case someone cares; I found the problem. Apparently I had defined

JUCE_CHECK_MEMORY_LEAKS to both 1 & 0 over the code for some reason. Obviously things get fcd up.