Hopefully your code is: updateComplete=this.callLater(setVerticalScrollBarMethod);
Depending on what that code does, it might use a bunch of memory, but if it gets freed later, it isn't a leak. The profiler will help you determine if there really is a leak. Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: [email protected] [mailto:[email protected]] On Behalf Of Manu Dhanda Sent: Monday, February 09, 2009 8:21 PM To: [email protected] Subject: [flexcoders] DataGrid updateComplete causes lots of memory leak. Hi Guyz, I have a viewstack holding two DG's. When I double click on an item in first DG, it should switch to the second DG and select the corresponding item in that DG and scroll down to that item. If I set verticalscrollbarposition something like.. updateComplete=this.callLater(setVerticalScrollBarMethod()); It causes a lot of memory leak until unless it is switched to the final view(2nd DG with highlighted item.) Can anyone tell me what I can use as an alternative to updateComplete ?? -Manu. -- View this message in context: http://www.nabble.com/DataGrid-updateComplete-causes-lots-of-memory-leak.-tp21927484p21927484.html Sent from the FlexCoders mailing list archive at Nabble.com.
