Thanks Alex. That's all pretty helpful. Brandon
--- On Fri, 10/9/09, Alex Harui <[email protected]> wrote: From: Alex Harui <[email protected]> Subject: RE: [flexcoders] Flash OCX Error To: "[email protected]" <[email protected]> Date: Friday, October 9, 2009, 5:07 AM Less is more. The fewer HBox and Canvas tags and more UIComponent tags will take up less memory and run faster. Occasionally there can be a Flash Player bug that will cause it to crash, but the two leading causes are running out of memory, and stack overflows. Checking the process memory can eliminate or rule-in the first. If your browser is using up more than 500Mb of memory, you could be running out of memory. The way I diagnose these problems is to start commenting out parts of the app to see if there is some portion of the app that makes a difference. You may see extra instances of an class if that class generates supporting objects within the player. The profiler only knows what is on top of the actionscript callstack and can’t see what is on the player’s internal callstack. Alex Harui Flex SDK Developer Adobe Systems Inc. Blog: http://blogs. adobe.com/ aharui From: flexcod...@yahoogro ups.com [mailto:flexcoders@ yahoogroups. com] On Behalf Of medconference Sent: Thursday, October 08, 2009 11:35 AM To: flexcod...@yahoogro ups.com Subject: [flexcoders] Flash OCX Error Hello, this is my first post! I have a large Flex app I'm trying to profile and make more efficient. I have some basic questions about profiling in general and application development as it relates to efficiency and performance. I have a few different item renderers which are based on HBox, have several embedded images and adds and removes these images from the HBox based on the data values. Occasionally, when a user interacts with a List or Drop-Down (one using a custom renderer), they get a Flash Ocx error. This is impossible to debug as there is no further info. The browser is then forced to crash. Is this most likely a memory or CPU issue? Most of my custom components are based on a Canvas stored in a .mxml file. When resizing my app I see CPU spike. Would basing my components on a UIComponent help this? In terms of profiling, I can see my app has 5 cumulative instances but 1 current instance. Why would there be 5 cumulative instances of the main application class? How is that even possible? Thanks! Brandon
