Profiling an app for memory leaks (as it will be running continuously).
Starts and stops threads, and calls web services. When profiled with
AQTime Allocation profiling the first web service call fails with an "access
violation - read of address xxxxx" (not zero address). When AQTime
Allocation profiling is not used it runs fine. Catch-22.
Q1 - Anyone have any idea where to start hunting?
So I instead turned on FastMM4 diagnostics which show no memory leaks. (ie
Q2 - apart from more detail is there anything that FastMM4 memory
diagnostics might miss that AQTime will pick up (ie do I need to get AQTime
working if FastMM4 is happy).