Thanks for the post. I was the one having a lot of memory issues. It really was not from caching issues. Mine was from loading several modules at the same time and placing them on the display list. My fix was still load them all at the same time, but don't place them on the display list until the user clicks the tab the module was to go into. That took my memory usage from over 800M to just over 200M even after clicking on all modules and getting them rendered.
But for the article, I did not download the code and test it, but we did something very similar. The problem we see is that it only caches the module for that session. If the user goes back and forth between modules it will use the cache. But we still see modules NOT cached at the browser. Every time we close the browser (tried IE, FF, and Chrome) it redownloads the module. Every time. Dale From: [email protected] [mailto:[email protected]] On Behalf Of Eric DeCoff Sent: Saturday, October 02, 2010 8:00 AM To: AFFUG Subject: [AFFUG Discuss] Flex Memory Growth ( Fix ) Hey All, Remember someone having issue with memory growth, and thought I'd post a link I came across http://ria-coder.com/blog/truly-cached-flex-modules -- Eric R. DeCoff Changing the world, 1 line of code at a time ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
