I should say i am using SDK 4.6 maybe time to move ? As I moved in and out of the view stack the memory goes up then droops back
I can see when I change view stacks for 3 to 4 the old instance in view stack is GC, memory drops as each component in the VS is dynamic and created when i move to the VS ID, think of a lesson ID 3 is the page, i moved form page 1 to page 2 etc, can you force the VS to GC when i finish with say ID3, today i see thew old object, wait 5 second, then true new object is created also I am seeing methordClouser memory (1971604 22.5%) Vector.<*> (1170776 13%) and Vector.<Number> (985760 11%) I do have a lot of skins, all using vector graphics peck memory so far is 134438K is this big ? so if this is not a memory leak, why the slowest changing view stacks ________________________________________ From: Mark Line [[email protected]] Sent: Tuesday, February 25, 2014 8:18 PM To: [email protected] Subject: Re: Slow view stake on Microsoft but not Mac or Chrombook If you have Flash builder installed you can easily check via the profiler. Change between viewstacks and try to force garbage collection within the profiler. Even doing this once will show if the previous view has been cleared up. (You might not see the memory drop straight away as the way the GC works but the instances will be cleared). I found the best way to check if filter on a package of a custom component and see how many instances are left. If its leaking it should be pretty clear On 25 February 2014 20:05, Scott Matheson <[email protected]> wrote: > Hi > My end users 5 of them, are telling me that on their "old" W7 PCs, a > mixture of devices they are all seeing 20sec to 120 sec to change from one > screen to the next, theses are simple viewstack changes > > each component in the view stack can be complex, working at the lower > level changing between view stack seems to be fine > > maybe this is a memory leak problem, I was thinking (maybe wrongly) that > as I move form view stack ID 3 to 0 all object created in index 3 (dynamic > item renders) would be cleaned by garbage collection, this may not be > correct as the components all access a singleton, which is never deleted, > would this stop the "old " component from being deleted so i am ending up > adding the component time and time again ? > > > > <mx:ViewStack id="masterNavigation" x="0" y="0" width="100%" > height="100%" change="masterNavigation_childIndexChangeHandler(event)" > > selectedIndex="{_uofsModel.activeMainMeunScreen}"> <!-- controling the > size of the pages with in the overall screen --> > > <ns:Login id="login"/> <!-- index 0--> > > <ns3:Pips id="pips" /> > > <ns1:Workmenu id="workmenu" /> > > > > <ns4:GoToPage id="GoToPage" /> <!-- 3--> > > <reports:StudentProgressReport id="studentReport" /> > > <!-- dynamic added seciotn at this ing 5 --> > > > > <s:NavigatorContent> > > <lesson:Lesson model="{_uofsModel.currentLessonModel}"/> > > </s:NavigatorContent> > > </mx:ViewStack> > > > ________________________________ > > Disclaimer: This electronic mail and any attachments are confidential and > may be privileged. If you are not the intended recipient, please notify the > sender immediately by replying to this email, and destroy all copies of > this email and any attachments. Thank you. > ________________________________ Disclaimer: This electronic mail and any attachments are confidential and may be privileged. If you are not the intended recipient, please notify the sender immediately by replying to this email, and destroy all copies of this email and any attachments. Thank you.
