Same problem exactly. Also no flashlog.txt generated when running application in flash player 10.1* debugger in both IE and FF/Chrome.

Any idea whould be great.

Has anyone had any luck with the following: http://arielsommeria.com/blog/2008/12/22/getting-the-flex-profiler-to- work/ ?  If so, which part seems to solve it for you?

Good point Anirudh. Do check if the brwoser is already open. Close all instances of the browser before start.

In addition do the following:

1. Please do check if debug version of Flash Player is installed (I think it should be since you are able to debug, but still cross check). You can check the version and if its debug or not by going to the following site:

http://kb2.adobe.com/cps/155/tn_15507.html

2. Please send us the Player version number displayed in the site above.

Regards,

Anand Gaurav.

Yes it does.

The newest version of chrome comes with in built Flash Player which doesn't get uninstalled/reinstallled with debug player. Try using Firefox and install debug player. Check on the same site if you are indeed using the debug player. In the meantime, I will get you the procedure to install the debug player on Chrome.

Regards,

Anand Gaurav.

People, does anybody success profiling in Flash player 10.1?

I've tried it on  a couple of comps with Windows XP on them.

IE and FF both give no result.

I can see that when I heat profile, mm.cfg gets edited with

apropriate line that is path to profile agent.

Also if there are exception, they are thrown in all

the browsers.

But no profiling and also no flashlog.txt is generated.

So can any of you guys actually profile successfully in flashplayer 10.1?

I have the same issue but with an Air application.  I tried reverting to 10.0 but still having the same problem.

I was using FB 4.0 but upgraded to 4.0.1

No Difference - still says Unable to connect to the application to fetch profile data.

Windows 7 - 64Bit Professional

Player Version: WIN 10,1,53,64

Debug: YES

Flash builder 4.0.1

I have only one mm.cfg and moreover,

I can see that a line is added to mm.cfg with the right path and port to profile agent when I try to run profiler

but then profiler stops with an error mentioned above

Just some updates:

I had been interacting  over connect sessions to lemtz over the same issue. Though I could see the problem, couldn't get to the root cause of the problem.

I asked him to roll back to 10.0 player and it works absolutely fine there.

I am still investigating this issue. In the meanwhile will try to get a pair of eyes from Flash Player team too.

Regards,

Anand Gaurav.

Someone mentioned on one of the JIRA bugs that he thought wmode="opaque" was interfering with the profiler and removing it made the profiler work for him. Do any of you have that set in the params?

Heidi

we have the same problem

we are on a Active directory domain and our home path is set on the user network drive.

when i log on a local acount the profiler start working!

so i went back on a domain account and i use wireshark too analyse what the program is trying to do.

i found out that it was searching for the mm.cfg on the user network drive. so i copy the mm.cfg of the document and setting/username/ folder

on the network drive and the profiler start working ! Great!

but the probleme is that the application doesn't reedit the good mm.cfg (in the network drive) so its start to bug in debug mode.

its seems to be because of the profiler agent being call by the mm.cfg

so what can cause  flash builder to editing the mm.cfg in document and setting/username/ folder and using the one in the home path?

i hope someone will find and answer to this question.

Quote:

     "A related bug to sebastiensb's issue seems to be this: http://bugs.adobe.com/jira/browse/FB-19102

     Can you see the similarities here ?"

I could not see similarities in my case. My  desktop is set to default location:

"%USERPROFILE%\Desktop" in registry.

Still cannot profile in 10.1 (see my posts above for details)

Flashbabaika,

I was completely unable to reproduce the issue despite several attempts. The problem is the reason for this issue seems to just elude me. Can you list down your system details specially if some special configuring related to network is done on your system ? e.g. dual network cards etc ?

Had the problem fixed with 10.1 for about a month with statically setting the ip to 127.0.0.1, however now we're back to a point of failure it seems.  Previously only IE would work and now IE is failing as are all other browsers.

This is absolutely an insane problem.  We have no other choice than to use 10.1 for our project and therefore we're hamstrung right now from having this problem. 

Adobe Flash Builder team, will you please step up here and help us all out?  We are really tired of having this unresolved and it should be embarrassing that it is not an isolated issue.