It may mean that the TitleWindow itself doesn’t have any non-circular references to GCRoot. But one of its children can.
The Flex 4 profiler tries to eliminate circular references so it won’t always show that a child is hooked to GCRoot because the child references the parent and vice-versa and that is a cycle. Check each of the children and other subobjects in the TitleWindow. On 6/11/10 2:54 PM, "reflexactions" <[email protected]> wrote: I am tring to figure out why when I open and closed a TitleWindow everything is fine but when I open two and then close two one doesnt get GC'd. Using the profiler and looking at the obvious, one TitleWindow is clearly stuck in memory but when I click on it and expand paths it says 0 paths. So if there are no paths why wasnt it GC'd? -- Alex Harui Flex SDK Team Adobe System, Inc. http://blogs.adobe.com/aharui
