On 4/9/15, 8:59 AM, "Oleg Konovalov" <oleg...@gmail.com> wrote:
>Alex, > >That profiler problem happens much before I reach my heavy duty popup with >many children, >on initial screen. >We are making calls to about 30 Stored Procs to get proper permissions and >load static data. >(can probably turn off some of them and only use data relevant to screen >with popup we need,although it might take time to investigate). > >As I said, Debugger is running fine, no timeouts whatsoever. > >Is Profiler more demanding than Debugger? Yes, the profiler is logging data for every line of code and every memory allocation. So if there is too much work to get the app up and running you can have this sort of problem. I’ve never actually dealt with this situation myself. IMO, it is an indicator that you could refactor the app and defer some of the work and see faster startup time and allow the profiler to do its thing. One thing you could try is to call pauseSampling() in a preinitialize handler in the app. That might shutdown the logging and allow the app to start up faster. Then call startSampling at the right moment to start collecting the data you need. Here’s the doc: http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/sa mpler/package.html#pauseSampling() -Alex
