Using Flex Builder 3 :
I have been getting this problem in every single debug launch for past few hours.
I used to get this earlier too, but once in a while, not with every debug launch.
I found out that flex debugger uses a certain 7935 port but I can't figure out
how to change it?
I remember getting this problem a few times. It might have to do with the Flex Profiler (I used to accidentally click that every now and then trying to launch the debugger).
If you start the Profiler and stop it too fast, it will add something to a file in your home directory that it shouldn't.
Check out /path/to/home/mm.cfg on your operating system (on mac, you can open it in textmate with mate ~/mm.cfg). The mm.cfg file stores some information about debugging in Flex
Then in that file, make sure this is the only content:
ErrorReportingEnable=1
TraceOutputFileEnable=1
If there's an extra line (can't remember/find it, something like PreloadSwf=/Users/[username]/Documents/workspace/.metadata/.plugins/com.adobe.flash.profiler/ProfilerAgent.swf?host=localhost&port=9999), delete it.
Let me know if that fixes it.
Lance
Also just make sure you're not using Chrome. Flash Player debugger (at the time of writing this) does not work in Chrome.
This worked for me: right click on a SWF, select "Open with...", choose "Other...", select the Debug player and check the "Always Open With" checkbox.
Mac OSX / FlashBuilder4
Right click your launched flash application, either in the browser or standalone flash player and click on debugger if enabled and change the radio button from localhost to other machine and enter the ip 127.0.0.1 and you are free to debug. I guess the problem maybe from your host file.
Changing the browser from default (chrome) to IE worked for me
Similar to danjp - This started happening to me after a Flash Player automatic update. I simply reinstalled the debug flash players from the Adobe Flash Player download page and everything works as expected.
Make sure there is a swf file with the proper name in your bin-debug directory and that name matches the swf name specified in index.template.html file for the project.
I had replaced index.template.html file by mistake with a similar one from another project. When I tried to debug, I got this "Waiting for flash player to connect to debugger…" status till it timed out.
To me the problem was that internet explorer opened and showed a certification problem, if i didn´t continue this the debugger would show this error. If i continued on ie, no problem happens.
Related
I am using VS2010 on Windows XP pro (sp3, x86), and I just installed the hotfix kb2106584. This fix was reported by some people, example here, as having a fix for an issue I had with Asp.Net Development Server not getting opened properly from VS, which I was having previously. My issue was being caused by ESET NOD32 messing with the http traffic from devenv.exe and causing all the ports in my computer to get used up, however.
Anyway, as soon as that was finished, I opened my website back up, and clicked debug. Asp.Net Dev server pops up, which was what the hotfix was supposed to make happen, and then notepad++ opens with the tabs I had last time I used it, and IE never shows up. "Wait, what?" try it again. and again. Always notepad++, never IE, always with no new documents opened, just some completely unrelated stuff.
I've seen one other post on SO about this happening, here, but his issue was corrupted files/filesystem. My project is in source control, so I tried a delete&revert to yesterday's revision. Still opens notepad++, so that's not my issue.
I've also tried rebuilding, which did nothing, and deleting my local Solution files, which also did nothing. I restarted the program and then the computer, both to no avail.
I start to believe that this is the hotfix screwing things up, so I try to do a system restore to a couple days ago. Once again, no dice; it's still pulling up notepad++ instead of IE.
So, the questions become:
Is there a setting or two I can try changing to make it open the proper program again?
Or was this a bad/improper hotfix, and if so, how do I uninstall it? It doesn't show up in the Add/Remove Programs dialog, and I don't see an option to uninstall it in VS, or in the installer.
Thanks in advance.
[edit] Also note: Notepad++ is not actually opening the website file, it's just getting opened with whatever I left in it last time. I dunno if this helps at all, but I felt like details would be appreciated. [/edit]
Fixed:
Uninstalling n++, deleting EVERY registry entry & folder containing 'notepad++' (except one, from whose string I removed ";notepad++.exe"), then reinstalling n++ made VS stop opening notepad++.
Now it opens the default web-browser again.
[edit]
Note for anyone else out there who ends up with this specific and bizarre problem:
It would be worth a shot to try changing the "Browse With..." setting in VS, by r-clicking on Default.aspx to "Internet Explorer". My list included Notepad++ as an available internet browser.
This might be a better solution than the previous, if it does in fact work.
I didn't know this setting would allow Notepad++ as an option until I had to set it back to IE again after all this, and that may have been the problem all along. Apparently, VS just changes this setting sometimes. How or why N++ got put in as an internet browser is completely beyond me, but I did myself the favor of 'Remove'ing NotePad++ from the list, and you may wish to do the same.
Again, I'll never truly know whether or not I nuked everything when I could have changed a single setting that got mysteriously reset, but may this [lesson?] at least be recorded for posterity.
[/edit]
It took all of that to figure out that it [was?] a bogus registry entry somewhere that [may have been?] modified by the hotfix; a registry entry that neither notepad++ nor visual studio 2010 ultimate would clean up on uninstall or replace on reinstall
Which was it? I have no idea. Like I said, I didn't even use n++ this week until VS started opening it for me, and the only change I made was to install that hotfix.
I'm a C++ programmer, but I'm a newbie in Flex. I'm developing a Flex 3 application for a social network using the FlashDevelop. For debugging I'm using the stand-alone FlashPlayer (10.3 debug) downloaded from Adobe. The application is a simple audio player which shows artist/album images.
The application worked properly on both local computer and remote server until I made some layout changes in Main.mxml. I added some HBoxes and changed Image placement. After that the application still works on my local computer, but it doesn't work properly after I upload it to a server.
Application buttons are not highlighted on over/out/click events, images loaded from the Internet are not displayed, text changed dynamically is not displayed, but when I click buttons a sound file is loaded from the internet and starts playing. It looks like some events which are responsible for components displaying are not dispatched, because some part of functionality not related to displaying still works.
To make sure that this is not a server problem, I rolled back to the previous revision. All works fine.
I suppose that this is a known issue, but I have no idea what is the reason.
Could anyone please help me to resolve the issue?
Thanks.
UDP: I observed the issue in IE and FF, I didn't test Opera and Chrome.
Are you tying to access the pixel data of the images in the new version? If so, that might be the problem, as pixel data for loaded images is not (always) accessible so that might throw a security error, which in turns breaks the rest of the interface.
Also, did you try running the remote version in the debugger? If so, is there any exception being thrown?
And no, it's not a known issue, it's the kind of annoying and hard to debug error that you sometime get when using the Flex SDK.
I have a problem with Visual Studio 2010. When I start debugging it works slowly.
Internet Explorer opens, but the website loads extremely slowly.
My workmate and me work on the same project and he doesn't have any problem like that.
My hardware is 4G memory + Intel Core i5 CPU 3.20 GHz.
I stopped my anti-virus program but it couldn't be resolved.
I've had the same problem for over a year! And I solved it :)
I took me about 20 seconds to start debugging, and about 1 minute to stop it. It also took 2 minutes to load the solution! My colleague had NO problems with the same solution.
I found my way out of it by a coincidence.
I CHANGED the NAME of the solution, and things suddenly happened 30 times faster.
I CHANGED the solution name back and it slowed down again!
This is probably a FUBAR error made by the Microsoft development team. Don't try to figure out why it happens :)
This might be a IPV6 issue (that shows itself in windows vista/7 when using firefox or IE). I've had that at work and this is what made pages load instantly when using localhost (instead of the 20+ seconds that could happen on image-heavy websites I was developing).
IPv6 (taken from Firefox cannot load websites but other programs can )
Firefox supports IPv6 by default, which may cause connection problems on certain systems. To disable IPv6 in Firefox:
In the Location bar, type about:config and press Enter.
The about:config "This might void your warranty!" warning page may appear. Click I'll be careful, I promise!, to continue to the about:config page.
In the Filter field, type network.dns.disableIPv6.
In the list of preferences, double-click network.dns.disableIPv6 to set its value to true.
For Internet Explorer, try using http://127.0.0.1:PORT_NUMBER/ where PORT_NUMBER is the port you can see in your address bar. If the loading of the page is faster, then you might want to go check the C:\Windows\System32\drivers\etc\HOSTS file and make sure the only line mentioning localhost looks like 127.0.0.1 localhost.
Check to see if you have _NT_SYMBOL_PATH environment variable set. Getting symbols or pdb files for the assemblies used by your application from a symbol server could be the cause of the slow startup of your application when debugging. You can also look at the symbols setting in VS>Tools>Options>Debugging. Also, take a look at the output window and the status bar down at the bottom in VS when your app is loading and taking a long time to see what VS is busy doing.
Not sure if this applies to ASP.NET applications, but disabling the 'Show Parameter Values' option in the Call Stack window's context menu considerably speeds up the debugger on my machine.
Two things to check.
1. Remove all the parameters in the watch list.
2. Build >> Config Manager , Check the Configuration Mode: Debug/Release.
I have encountered the same problem. I could make it better by deleting the Folder created in the temporary aspnet folder. For that you need to close the solution that you have opened and then delete. I don't know if there is any other solution.
I just finished my installation of Adobe Flash Builder 4. I've definitely installed the most recent flash player from Adobe's website onto my computer. Also, in the run configurations of flash builder 4, I changed the source path from the .html file to the .swf file that is generated. I don't need to test it in a web browser, I just want to run the swf in flash player.
I only have 1 .as file in my actionscript project and there is no code written in it other than the package, class and main function statements. When I run the .html file, it runs fine, and debugs fine. However, when I switch the source path to the .swf file, it runs fine but doesn't debug!
When I debug it, the progress gets stuck at 57% and it says "Waiting for Adobe Flash Player to connect to debugger..." in the "Progress" tab. After a few minutes a window pops up that says:
"Failed to connect. The session has timed out. Ensure that you have run the application with debugging on and that I have the debugger version of flash player."
What can I do to fix this? I am on an intel Mac running OS 10.6.5.
Thanks
You say you installed the most recent Flash Player, but you don't say if you by that mean the debug player. The "Flash Player 10.1 Plugin content debugger" and "Flash Player 10.1 Projector content debugger" can be downloader at http://www.adobe.com/support/flashplayer/downloads.html
This might solve your problem
http://blog.air4android.com/?p=59
HTH
I had exactly that symptom.
I cleaned all related projects, removed bin-debug and bin-release, cleaned the cache, reinstalled the debug version of the player. It didn't help. I was about to reinstall FlashBuilder.
Then I displayed the javascript console. I saw there is a syntax error in my index.template. As a result, the application was never started, so the screen remained blank and the debugger failed to connect.
I fixed the silly error and it worked again! Basically, that message tells you the application failed to start.
Make sure you're not using Chrome. At time of writing Flash Player debugger does not work in Chrome.
I had this problem and simply switched the web browser to Safari in Flash Builder preferences.
what worked for me finally was copying the swfobject.js to the bin-debug folder. I don't know why it wasn't there, but that fixed the problem.
you do, of course, have to run a flash debugger version in your browser.
I have installed Flex Builder 3 and Flash Player 10 on my machine.
I don't know where the trace output goes because I just don't see it (I tried debug and output windows).
Also the breakpoints don't hit.
Salut Omule :)
If you press the Debug Icon(the bug thingy) or go to Run > Debug you should go to the Debugging perspective.
If might be handy to install the Flash Tracer plugin for Firefox to see your traces from the browser.
First you need to make sure you have the Debug version of Flash Player 10. You can do that by checking is Debugging is true using this test.
You can view traced messages in the console (Menubar - Window - Console).
But since you said that breakpoints are not hit, I guess the problem is somewhere else. Make sure that you are debugging instead of running the app (select Debug from the Run menu or just hit F11 while at the corresponding mxml file).
If that doesn't help, and if you are on Firefox, try uninstalling the last addon that you installed. Some addons (including older versions of google toolbar and adblock plus) have known to block swfs from connecting to the flex builder's debugger.