This isn't so much a question as a comment. I got the above error; I had a vi that worked and then stopped working when I made some really minor change in the detail, giving me the memory.cpp line 638 error. I am using an event structure and the mods.doubleclick feature on a "mouse up" event and doing this double click would provoke the error.
Unlike much discussion on this error message in other threads, I am not knowingly using any custom dll's nor any type casts- but they might be buried somewhere in subVI's written by colleagues.
After reading all the other discussion and concluding that it didn't apply, I used probes to discover precisely how far the code would get before crashing out, then deleted the wires linking the bit that worked to the bit that didn't, then drew new wires on.
For the moment, the code works, but we'll see if it comes back again.
Any thoughts anyone?
John
