Can you try to set the data provider to null before calling unload? Objects will stay in memory as long as something else has a strong reference to them. Here's a few references I found on it, http://dreamingwell.com/articles/archives/2008/05/understanding-m.php, http://blogs.adobe.com/aharui/tag/modules-memory-leaks,
On Tue, Apr 8, 2014 at 11:12 AM, Davorian <don.fasa...@gmail.com> wrote: > Hallo All, > > I hope I'm wrong on this one but that doesn't appear to be the case. > > I have created a JIRA and sample project is attached to the JIRA. > > Basically, I have a simple test module with a populated spark dataGrid > that > gets loaded into a shell application. I attempt to unload this module and > it > doesn't unload. If I don't populate the spark datagrid, it will unload. If > I > use an mx dataGrid and populate it it will unload. > > This is preventing modules from unloading in our enterprise application. > I'd > like to know why this is occuring and I will happily resolve it given some > advice whether it's a Flex SDK issue or our own code, compilation settings. > > Regards, > > Davorian > > > > -- > View this message in context: > http://apache-flex-development.2333347.n4.nabble.com/In-Apache-Flex-4-10-and-4-12-why-does-setting-a-dataProvider-on-a-spark-datagrid-prevent-the-module--tp36715.html > Sent from the Apache Flex Development mailing list archive at Nabble.com. >
