Alex,
 
Is this still an issue?  I got the impression it had been addressed in
swfobject 2.1.
 
Jeff

        -----Original Message-----
        From: flexcoders@yahoogroups.com
[mailto:flexcod...@yahoogroups.com] On Behalf Of Alex Harui
        Sent: Thursday, February 26, 2009 11:36 AM
        To: flexcoders@yahoogroups.com
        Subject: RE: [flexcoders] Flex & RAM memory use - (probably a
question for the player engineers?)
        
        

        Are you using SWFObject?
http://groups.google.com/group/swfobject/browse_thread/thread/d94bc23037
ddc714

         

        Alex Harui

        Flex SDK Developer

        Adobe Systems Inc. <http://www.adobe.com/> 

        Blog: http://blogs.adobe.com/aharui
<http://blogs.adobe.com/aharui> 

         

        From: flexcoders@yahoogroups.com
[mailto:flexcod...@yahoogroups.com] On Behalf Of Ashish Verma
        Sent: Thursday, February 26, 2009 5:27 AM
        To: flexcoders@yahoogroups.com
        Subject: Re: [flexcoders] Flex & RAM memory use - (probably a
question for the player engineers?)

         

        For the first problem I don't have clue but for second problem I
can say that it's due to weird behaviour of Flash Garbage Collector.  

        On Thu, Feb 26, 2009 at 2:48 PM, nwebb <neilw...@gmail.com>
wrote:

        Hi, 
        
        we're having 2 issues with memory in Flex:
        
        1) Part way through our Flex application we open an external
HTML page (3rd party page). The user selects items from this page and
then closes the page & the control is then returned to the Flex
application. This 3rd  party page is heavy in terms of memory, and that
memory is never getting released once the page is closed. Is it at all
possible that Flex is holding on to a handle to that page and if so is
there any way to release it, or is this definitely not a Flex problem,
and more a browser issues or issue with the external page as I expect?
        
        2) The Flex app is one part of a much larger website. When we
proceed past the Flex app (ie the user proceeds to a page where the app
isn't embedded), again much of the memory Flex was using doesn't seem to
be getting released. A browser issue?
        
        Needless to say IE seems to be much more of a memory hog, but
we've been looking at this in both IE and FireFox.
        
        Any help much appreciated.
        
        Cheers,
        Neil
        
        
        
          

         

        



        

Reply via email to