Hi,

I have also faced this issue that was due to update of flash player.
Neither I am able to debug nor profiling and one more issue with profiler,
if your application take time to load likewise it is loading data from
server then my machine got hanged or profiling does not working. To resolve
this issue I have created local data resources and my profiler worked
properly.

For profiling you should have a valid license of flash builder.

Regards,
Manish
I tried to create brand new HelloWorld,
but got the same exact error in FB4.5.1.
A lot of people on the net got the same.
Did that profiler ever worked?
On Apr 10, 2015 14:17, "Alex Harui" <aha...@adobe.com> wrote:

> Did you try profiling a really simple “Hello World” type of application?
> There could be some issue with how the profiler talks to the SWF.  I think
> it uses a Socket.  Maybe something else is using that socket.
>
> -Alex
>
> On 4/10/15, 11:03 AM, "Oleg Konovalov" <oleg...@gmail.com> wrote:
>
> >I don't think that is the issue.
> >
> >I tried profiling simple application (showing a graph with few nodes,
> >using
> >RaVis library - sample of what we have on one screen),
> >and got exactly the same error popup "No activity happened in the past 60
> >seconds
> >after connection was established with the application"  and only after
> >that
> >app came up.
> >
> >Is there anything I need to do to configure FB Profiler to run it?
> >(i haven't done that in Flex before....)
> >
> >
> >On Thu, Apr 9, 2015 at 3:46 PM, Alex Harui <aha...@adobe.com> wrote:
> >
> >>
> >>
> >> 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
> >>
> >>
> >
> >
> >--
> >Thank you,
> >Oleg.
>
>

Reply via email to