-
photography by Kristel van Beek
23 Dec: Google Chrome and why I use it for Flex debugging
posted by: martijn, at 23 December 2008 9:53 GMT+1, 23 December 2008 13:48 GMT+1
Google Chrome on Windows is my new default browser at work (I use Mac at home, Windows at work). It is perfect for debugging my Flex apps because since Flex Builder 3.0.2 update debugging is working not perfect. Flex builder freezes my complete system trying to get a connection with the debug player. 40% of the time it failes :(Here comes my love for Chrome, it detects Flash Player crashes and stops the plugin (although it still costs a lot of time). A problem with Chrome for normal usage is it's failure with the Adobe Feeds page, it cannot open the links.Write a comment for this articleOn my Mac at home I don't have the same problems with Flex Builder 3.0.2, so it could be a Windows problem.
I filled a bug on bugs.adobe.com
3 Comments
Write a comment for this article-
Dan Hamm says:
at 12 August, 2009 13:20 www.hamm.co.ukNot sure how to interpret you comment about hanging, but Chrome does not seem to work in debugging mode. Chrome stops responding (fine) but I cannot get to the debugging window! -
Dan Hamm says:
at 13 August, 2009 17:12Found the answer on http://polygeek.com/tag/flexbuilder-tips - look for Chrome Cache Issue. Apparently Chrome caches relentlessly. You switch it off with the -sandbox parameter in the parameters box when you edit the browser properties -
Lawrence says:
at 12 February, 2010 20:53 show-desktop.blogspot.com/Debug in Flex (Flash) Builder with Chrome Browser: http://show-desktop.blogspot.com/2010/02/debugging-in-flex-flash-builder-with.html
-
All rights reserved |
Design and Development by Martijn van Beek |
Managed by Flexibility |
Photography by Kristel van Beek
You have Flash Player version: (click to check if you got the latest)
You have Flash Player version: (click to check if you got the latest)