Re: [flexcoders] Frustrations with the profiler - analyzing memory usage.

2013-02-06 Thread Alex Harui
I have never seen the localconnection hack fail to GC everything, but it has been over a year since I was last in the profiler, so maybe more recent players don’t GC everything, but I would be surprised if that was the case. That’s because the LC hack wasn’t supposed to GC everything, but once

Re: [flexcoders] Frustrations with the profiler - analyzing memory usage.

2013-02-06 Thread Nigel Magnay
Thanks for that - that's very helpful information. I'm getting dragged into diagnosis because on very low-spec machines our app is tending to eat memory causing it to heavily slow down. I've managed to diagnose some of these (use of setTimeout, Bindings that never go away) which is liable to help

Re: [flexcoders] Frustrations with the profiler - analyzing memory usage.

2013-02-05 Thread Alex Harui
The true test of a leak is whether your OS’s process manager says that memory consumption keeps going up. Before we had a profiler, we would add code to the app to exercise some sequence (by faking button events, etc), force garbage collection, and report System.totalMemory over and over again

[flexcoders] Frustrations with the profiler - analyzing memory usage.

2013-02-05 Thread Nigel Magnay
We have an application that is leaking memory. Sadly, trying to diagnose this with the flex profiler (4.6, 4.7) is proving to be a frustrating experience. I've picked on one object class to try and understand what is going on. We have a wizard-style dialog box with a sidebar control 'wizardlinks'