Hi Anand,

Using addPopup which also the same impact

The profiler still showing the same peak display and keep on
increasing it open several time!


       private function Find_Rec():void
        {
        popfind = new uMasterGridSearch;
                popfind.title = "Find Screen for Material Master";
                popfind.myArray = model.material;
                popfind.sData = "sMaterialName";
                popfind.sTable = "Material";
                popfind.sColumn = "MaterialName"
                popfind.addEventListener("close", PopCancel_Find,false,
0,true);
        PopUpManager.addPopUp(popfind, this, true);
        PopUpManager.centerPopUp(popfind);

        }

                private function PopCancel_Find(event:Event):void
                {
                        
PopUpManager.removePopUp(IFlexDisplayObject(event.currentTarget));
                }




thanks

raaja


On Oct 14, 3:31 pm, "<mx:AnandVardhan/>" <[EMAIL PROTECTED]>
wrote:
> dude the problem is
>
> PopUpManager.createPopUp
> createPopup is creating poup instance each time, which causes multiple
> instance of object set listening your event and causing memory leaks.
> flash garbage collector never removes anything which is listening.
>
> So its better to use addPopup which will create one and only instane
> all the time.
> I hope am clear enough :)
> Anand
>
> On Oct 14, 3:27 pm, raajasoft <[EMAIL PROTECTED]> wrote:
>
>
>
> > Hi Anand,
>
> > thanks for ur reply
>
> > use of weak useweakreference state also applied u can see below!
>
> > private function Find_Rec():void
> >         {
>
> >                 popfind =
> > uMasterGridSearch(PopUpManager.createPopUp(mx.core.Application.application
> > as DisplayObject,uMasterGridSearch,false));
> >                 popfind.addEventListener("close", PopCancel_Find,false,
> > 0,true);
> >                 popfind["cmdCancel"].addEventListener("click",
> > PopCancel_Find,false,0,true);
> >                 popfind["cmdOk"].addEventListener("click", PopOk_Find,false,
> > 0,true);
> >         PopUpManager.centerPopUp(popfind);
>
> >         }
>
> >                 private function PopCancel_Find(event:Event):void
> >                 {
> >                         PopUpManager.removePopUp(popfind);
> >                 popfind["cmdCancel"].removeEventListener("click",
> > PopCancel_Find);
> >                 popfind["cmdOk"].removeEventListener("click", PopOk_Find);
> >                 }
>
> > i can try with ur addPopup Method and get back to u,
>
> > raaja
>
> > On Oct 14, 3:21 pm, "<mx:AnandVardhan/>" <[EMAIL PROTECTED]>
> > wrote:
>
> > > Dude do not create popup every time using createPopup, instead use
> > > addPopup.
>
> > > The creation/deletion of popup is not the cause of memory leak, its
> > > the events attached to the objects within the popup causes it, so
> > > suggested use weak-references.
>
> > > Anand
>
> > > On Oct 14, 10:35 am, "mani china" <[EMAIL PROTECTED]> wrote:
>
> > > > It seems everytime you add, it create a new instance, you could use 
> > > > trace()
> > > > to see what happened~
>
> > > > On Tue, Oct 14, 2008 at 12:51 PM, raajasoft <[EMAIL PROTECTED]> wrote:
>
> > > > > Hi all,
>
> > > > > when i use popups dialogue (createPopUp/deletePopUp TitleWindow)
> > > > > memory Leak happen and when i close the popup still the memory used by
> > > > > the popup class(mxml file) still there (used flex 3.0 profiler ) .
> > > > > every time i  the popup of same class(mxml file) memory keep on
> > > > > increasing every time.
>
> > > > > thanks and waiting for reply,
>
> > > > > raaja- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Flex 
India Community" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/flex_india?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to