acidburn0zzz / flexlib

Automatically exported from code.google.com/p/flexlib
MIT License
2 stars 0 forks source link

Scheduling classes result in a memory leak #294

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Create a scheduleViewer
2. Initalize the entryLayout and entryRenderer on the schedule viewer
2. Add at least one scheduling entry
3. Null out reference to scheduleViewer

What is the expected output? What do you see instead?

No scheduling classes remain.  Flex Profiler shows references to
scheduleViewer, scheduleNavigator, schedule, entryViewer and
simpleTimeDescriptors.  Expanding the object reference shows that
scheduleViewer.navigator results in a _parent on schedule and _parent on
EntryViewer.

What version of the product are you using? On what operating system?

3.4 of FLEX. Windows XP.

Please provide any additional information below.

Attempted to clean up the leak however majority of the attributes on
scheduleviewer are private.  Classes also create event listeners which we
cannot access which also prevent these objects from being GC'd.

Ideally a dispose() method would be added to the ScheduleViewer that would
free up all required references.

Original issue reported on code.google.com by tjahe...@gmail.com on 9 Apr 2010 at 12:35