Comments on: Memory Leak in Flex 3.2 Lists & Grids http://workdayui.wordpress.com/2009/02/05/memory-leak-in-flex-32-lists-grids/ Just another WordPress.com weblog Tue, 01 Dec 2009 21:13:27 +0000 http://wordpress.com/ hourly 1 By: diaper pee girl http://workdayui.wordpress.com/2009/02/05/memory-leak-in-flex-32-lists-grids/#comment-461 diaper pee girl Mon, 20 Jul 2009 20:32:24 +0000 http://workdayui.wordpress.com/?p=28#comment-461 emm. thank you )) emm. thank you ))

]]> By: Hob http://workdayui.wordpress.com/2009/02/05/memory-leak-in-flex-32-lists-grids/#comment-429 Hob Wed, 06 May 2009 18:14:02 +0000 http://workdayui.wordpress.com/?p=28#comment-429 The error you're seeing isn't coming from StageEventProxy. StageEventProxy is simply calling the event listener which was registered. The error is actually being thrown from AdvancedDataGridBase. Unfortunately you'll probably just have to spend some time in the debugger to see exactly why this is being thrown. It might be a configuration problem on the grid, but more than likely its simply a bug in the grid. We come across them all the time. Question is: Is this a critical error... Meaning, once you dismiss it, does your app completely stop responding, or do you continue to be able to use it. If the answer is the latter, then I wouldn't worry too much about it. It'll only ever be a problem for folks running the Flash debug player. If its the former, you've probably got at least a 1/2 day of debugging ahead of you. The error you’re seeing isn’t coming from StageEventProxy. StageEventProxy is simply calling the event listener which was registered. The error is actually being thrown from AdvancedDataGridBase. Unfortunately you’ll probably just have to spend some time in the debugger to see exactly why this is being thrown. It might be a configuration problem on the grid, but more than likely its simply a bug in the grid. We come across them all the time. Question is: Is this a critical error… Meaning, once you dismiss it, does your app completely stop responding, or do you continue to be able to use it. If the answer is the latter, then I wouldn’t worry too much about it. It’ll only ever be a problem for folks running the Flash debug player. If its the former, you’ve probably got at least a 1/2 day of debugging ahead of you.

]]> By: Vijay Anand Mareddy http://workdayui.wordpress.com/2009/02/05/memory-leak-in-flex-32-lists-grids/#comment-428 Vijay Anand Mareddy Wed, 06 May 2009 17:54:40 +0000 http://workdayui.wordpress.com/?p=28#comment-428 Hey all was well until i unintentionally did a mouse drag i think somewhere on the AdvDataGrid... am getting an error at [C:\Users\hob.spillane\Documents\Flex Builder 3\SDK_18268_PATCH\src\mx\managers\systemClasses\StageEventProxy.as:40] TypeError: Error #1009: Cannot access a property or method of a null object reference. at mx.controls.advancedDataGridClasses::AdvancedDataGridBase/http://www.adobe.com/2006/flex/mx/internal::columnItemRendererFactory()[C:\work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\advancedDataGridClasses\AdvancedDataGridBase.as:1454] at mx.controls::AdvancedDataGrid/http://www.adobe.com/2006/flex/mx/internal::columnItemRendererFactory()[C:\work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGrid.as:2094] at mx.controls.advancedDataGridClasses::AdvancedDataGridBase/http://www.adobe.com/2006/flex/mx/internal::columnItemRenderer()[C:\work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\advancedDataGridClasses\AdvancedDataGridBase.as:1436] at mx.controls::AdvancedDataGridBaseEx/columnDraggingMouseMoveHandler()[C:\work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGridBaseEx.as:4916] at mx.managers.systemClasses::StageEventProxy/stageListener()[C:\Users\hob.spillane\Documents\Flex Builder 3\SDK_18268_PATCH\src\mx\managers\systemClasses\StageEventProxy.as:40] Hey all was well until i unintentionally did a mouse drag i think somewhere on the AdvDataGrid…

am getting an error at
[C:\Users\hob.spillane\Documents\Flex Builder 3\SDK_18268_PATCH\src\mx\managers\systemClasses\StageEventProxy.as:40]

TypeError: Error #1009: Cannot access a property or method of a null object reference.
at mx.controls.advancedDataGridClasses::AdvancedDataGridBase/http://www.adobe.com/2006/flex/mx/internal::columnItemRendererFactory()[C:\work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\advancedDataGridClasses\AdvancedDataGridBase.as:1454]
at mx.controls::AdvancedDataGrid/http://www.adobe.com/2006/flex/mx/internal::columnItemRendererFactory()[C:\work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGrid.as:2094]
at mx.controls.advancedDataGridClasses::AdvancedDataGridBase/http://www.adobe.com/2006/flex/mx/internal::columnItemRenderer()[C:\work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\advancedDataGridClasses\AdvancedDataGridBase.as:1436]
at mx.controls::AdvancedDataGridBaseEx/columnDraggingMouseMoveHandler()[C:\work\flex\dmv_automation\projects\datavisualisation\src\mx\controls\AdvancedDataGridBaseEx.as:4916]
at mx.managers.systemClasses::StageEventProxy/stageListener()[C:\Users\hob.spillane\Documents\Flex Builder 3\SDK_18268_PATCH\src\mx\managers\systemClasses\StageEventProxy.as:40]

]]> By: Alexey http://workdayui.wordpress.com/2009/02/05/memory-leak-in-flex-32-lists-grids/#comment-412 Alexey Tue, 24 Mar 2009 18:28:23 +0000 http://workdayui.wordpress.com/?p=28#comment-412 2Feng You should download Data Visualization for Flex 3.3 separately and unzip it to Flex 3.3. SDK folder http://www.adobe.com/products/flex/flexdownloads/#flex_DataVisualization 2Feng
You should download Data Visualization for Flex 3.3 separately and unzip it to Flex 3.3. SDK folder
http://www.adobe.com/products/flex/flexdownloads/#flex_DataVisualization

]]> By: Feng http://workdayui.wordpress.com/2009/02/05/memory-leak-in-flex-32-lists-grids/#comment-408 Feng Fri, 06 Feb 2009 20:33:21 +0000 http://workdayui.wordpress.com/?p=28#comment-408 i got your point, now i will dig into it. thanks. i got your point, now i will dig into it. thanks.

]]> By: Hob http://workdayui.wordpress.com/2009/02/05/memory-leak-in-flex-32-lists-grids/#comment-407 Hob Fri, 06 Feb 2009 20:06:30 +0000 http://workdayui.wordpress.com/?p=28#comment-407 No, the name doesn't matter. Just make sure you don't have the flex sdk source as a source path in your flex builder project. That will cause the changes in my patch file to be overridden by the default 3.2 code. No, the name doesn’t matter. Just make sure you don’t have the flex sdk source as a source path in your flex builder project. That will cause the changes in my patch file to be overridden by the default 3.2 code.

]]> By: Feng http://workdayui.wordpress.com/2009/02/05/memory-leak-in-flex-32-lists-grids/#comment-406 Feng Fri, 06 Feb 2009 19:52:49 +0000 http://workdayui.wordpress.com/?p=28#comment-406 the patch name is SDK_18268_PATCH.swc, do u mean i should change its name and drop it in lib folder to replace other lib file? the patch name is SDK_18268_PATCH.swc, do u mean i should change its name and drop it in lib folder to replace other lib file?

]]> By: Hob http://workdayui.wordpress.com/2009/02/05/memory-leak-in-flex-32-lists-grids/#comment-405 Hob Fri, 06 Feb 2009 19:20:53 +0000 http://workdayui.wordpress.com/?p=28#comment-405 Dropping the patch in your lib folder should replace the 3.2 version of StageEventProxy with the version in the patch file (which is the 3.3 version). If you're still seeing a memory leak it's probably a prioritization problem. I had that problem at first, because I had added the Flex SDK source as a source path in my project, and anything that's added as a source path gets a higher priority than things that are added as libs. Dropping the patch in your lib folder should replace the 3.2 version of StageEventProxy with the version in the patch file (which is the 3.3 version). If you’re still seeing a memory leak it’s probably a prioritization problem. I had that problem at first, because I had added the Flex SDK source as a source path in my project, and anything that’s added as a source path gets a higher priority than things that are added as libs.

]]> By: Feng http://workdayui.wordpress.com/2009/02/05/memory-leak-in-flex-32-lists-grids/#comment-404 Feng Fri, 06 Feb 2009 18:58:47 +0000 http://workdayui.wordpress.com/?p=28#comment-404 thanks for your fast reply. your understanding is totally right. i have put patch file in the flex builder lib. do u mean i don't have to change my flex code, it will work for me? because i have tested with it, but i did not see the expected change, so i upgrade it to sdk3.3 and met this issue. i hurt my left ring finger when i want get more mango from its core, so please forgive me not type any uppercase letters here. thanks for your fast reply. your understanding is totally right. i have put patch file in the flex builder lib. do u mean i don’t have to change my flex code, it will work for me? because i have tested with it, but i did not see the expected change, so i upgrade it to sdk3.3 and met this issue.
i hurt my left ring finger when i want get more mango from its core, so please forgive me not type any uppercase letters here.

]]> By: Hob http://workdayui.wordpress.com/2009/02/05/memory-leak-in-flex-32-lists-grids/#comment-403 Hob Fri, 06 Feb 2009 18:44:42 +0000 http://workdayui.wordpress.com/?p=28#comment-403 If I understand your problem, once you upgrade to the 3.3 SDK your compiler is saying it can no longer find the AdvancedDataGrid. That didn't happen for me, but you can always force the Pro libraries back into Flex Builder by adding a source path to the data visualization source. You should find it at %FBPRO_Install_Folder%/sdks/3.2.0/fbpro/projects/datavisualization/src. If you're still having problems, try just using the patch file I posted. If you simply drop that into your lib folder, it will fix the problem in the 3.2 SDK. If I understand your problem, once you upgrade to the 3.3 SDK your compiler is saying it can no longer find the AdvancedDataGrid. That didn’t happen for me, but you can always force the Pro libraries back into Flex Builder by adding a source path to the data visualization source. You should find it at %FBPRO_Install_Folder%/sdks/3.2.0/fbpro/projects/datavisualization/src.

If you’re still having problems, try just using the patch file I posted. If you simply drop that into your lib folder, it will fix the problem in the 3.2 SDK.

]]>