Yes, i can debug.
Try profiling a simple test case. I suppose if you're app is really slow on startup, the profiler may timeout waiting to hook up.
Flex SDK Developer
Adobe Systems Inc.
I tried to profile blank application. Same problem
I think, the message, that i get, have an important meaning and concrete reason ...
There must be the way to get it working.
Usually it has just been timing. FlashBuilder modifies your mm.cfg to add a preloaderSWF that is the profiler. The preloaderSWF loads first, then your app then they try to talk via sockets. The app SWF must be a debug SWF, not one exported for release.
I have the same kind of problem, and i don't think it's about timing, because if I start a blank project, add a label saying:' hello world' and a Alert to creationComplete event saying the same thing, add a breakpoint to the createComplete function i can debug this pretty ok.
But once i start profiling this, I get my app on the browser, working ok but in 15 seconds or so a get that exact same time out warning....
But since you pointed out that it uses the mm.cfg file, might it be a port problem?
I think i have seen a some kind of fix for that in the flex builder 3...could that be the fix in flash builder 4?
Try rebooting. That has always fixed it for me.
1. restart the program
2. restart the whole machine
3. crawl for an in the web at least a day
before posting anything here
Still , I also noticed that the first time that i debug a project once i have launched flash builder there is a warning that the debugger did not connect.
The profiler is actually handled by the Flash Builder team. Try posting on
Did you ever get an answer to this - I have the same problem