> We've been using this command for years and this problem only > surfaced recently. We haven't updated that plugin.
What did you change? Did the version of Active4D change? > Assuming this will show that we are leaking memory can you or others > recommend a way within a4D (or by calling 4D) to possibly capture where > we're leaking memory. Are there options besides AP Available Memory? The best way is to use Instruments from Xcode. Regards, Aparajita www.aparajitaworld.com "If you dare to fail, you are bound to succeed." - Sri Chinmoy | www.srichinmoy.org _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
