flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lyndon Fasanya (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLEX-34194) IIn Apache Flex 4.10 and 4.12 why does setting a dataProvider on a spark datagrid prevent the module it's from unloading from it's AIR application shell.
Date Fri, 28 Mar 2014 14:58:18 GMT
Lyndon Fasanya created FLEX-34194:
-------------------------------------

             Summary: IIn Apache Flex 4.10 and 4.12 why does setting a dataProvider on a spark
datagrid prevent the module it's from unloading from it's AIR application shell.
                 Key: FLEX-34194
                 URL: https://issues.apache.org/jira/browse/FLEX-34194
             Project: Apache Flex
          Issue Type: Bug
          Components: Spark: DataGrid
    Affects Versions: Apache Flex 4.12.0, Apache Flex 4.10.0
         Environment: Windows 7, IntelliJ12, Flex 4.12 SDK, Adobe AIR 3.8
            Reporter: Lyndon Fasanya
            Priority: Critical


I have patched a module unloading shell app from the internet converting it to an AIR (3.8)
application shell, to replicate the issue that I'm finding in our Enterprise Asset Management
appplication, which needs this fix!

I am using Adobe Scout to profile the application.

In my shell application I load a module using module loader into a child Application Domain.
The shell derived from Tom Sugden's module unloading application loads the module and like
I have found online the first instance is pinned in memory. I thought possibly adding ArrayCollection
and ArrayList in the shell app. would allow it to be removed but it doesn't I understand that
this could be due to somehow this 'setting of the dataProvider' causing the module to be registered
with the main app. I have looked in Scout and found the frame where the dataProvider is set
and still I cannot identify from the AS objects or the function calls what could be doing
it. Possibly it's a case of not knowing what to look for.

Some other things of note:
If I use an mx:DataGrid with same dataProvider the module unloads first time.
If I use a s:DataGrid with no dataProvider set the module unloads first time.
Even if I set a dataProvider on an s:DataGrid by pressing a button on the UI which caused
the dataGrid to appear and the unset by setting the grids dp to null the module does not unload.

I have a project created that one can use to debug this.

I would really like a solution for this and to be able to understand.

i have keep-all-type-selectors set to true in the main app even if I remove all custom styles
the problem remains.

I upgraded from 4.10 to 4.12.
I even generated a link-report from the main app and used load-externs in the module to optimise
any shared code defintions without success.

I think this bug is critical and understandably I do not want to use an mx:DataGrid.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message