 |
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Brian Raymes - [06/16/08 10:49 AM ]
I have been affected by this for some time now (RC1 through RC3) on Windows Vista Business w/ SP1. It's not just Mac. For me, the debugger in Flex Builder does not connect with the session, in fact, it terminates before the browser even launches.
Also happens on Win XP with SP3, firefox 3.0 RC3. Since firefox 3 will be available today (Jun 17), it's better to support it as soon as possible! Thanks.
Problem still persists with Flex 3 and the official Firefox 3 release, available today (6/17). This is pretty urgent; anybody who innocently installs Firefox 3 (as I did) has Flex development badly impaired. Help! (Using 9.0.0.115 under XP)
I just fell into this trap also .. Firefox 3 - flash player 9.0.124
I am also having troubles with Windows Vista Business SP1 and Flash player 9.0.124. In my case the debugger is always terminated, and if I have a breakpoint set, the browser crashes.
I should also note that I have disabled all extensions in my Firefox to ensure there were no conflicts with extensions.
I can reproduce this on both Mac and Windows. I'm in the process of investigating to try to get to the root of the problem.
I found that sometimes installing another program like Flash CS3 will mess up the debug player for Flex Builder 3. My solution is to install the Flash CS3 9.06 player update which has the debug player installer, and that fixes it. (See FB-13057)
Could this be a solution? This seems to be caused by the latest version of the Greasemonkey extension, in combination with Firefox 3. On both my Mac and my Windows machines, when I disable the Greasemonkey extension, the problem goes away. (If I run the most recent Greasemonkey on Firefox 2, Flex Builder works fine.)
(Jim Rutherford: The problem you are running into sounds different from the one reported in the "Steps to Reproduce." This bug is about debugging not connecting -- e.g. trace() statements don't show up, and breakpoints don't get hit. Can you please log a separate bug?) ACTION REQUESTED: Those who have run into this problem (the problem described in the repro steps, e.g. trace statements don't show up in the Console view), please post a reply here: - Do you have Greasemonkey installed? - If you disable it, does the problem go away? Im running on os 10.5 with the FF3 Final i reran the flash player installer from inside of the flex builder plugin folder and its unable to debug in firefox i dont have greasemonkey installed , it works fine inside of safari
Running FF3 Final with Flash Player 9.0.124 (debug) and can confirm that disabling Greasemonkey from the addons window fixes the debugger problem in my case. (Win XP)
greasemonkey is not installed on FF and the problem persists. Tried to re-install 9.0.124 debug version but no luck.
Disabling Greasemonkey solved the problem.
This isn't really a permanent fix though, but is the problem with Greasemonkey, Flash or Firefox? WinXP, FF3, FP 9.0.124 debug , NO Greasemonkey . Debug no work
Mac OS X 10.5.3, FF3, FP 9.0.124 debug version, NO Greasemonkey, Debug not working
I had the Firefox Plug-In "Adblock Plus" installed.
I uninstalled this Plug-In and now DEBUG IS WORKING! I had Adblock Plus installed so i uninstalled it now it debugs
Google Toolbar (v3.1.20080605W) is the culprit for me. Disabling this extension caused the debugger to work as expected. Looks like I forgot to disable this one during my initial testing.
Disabling Flashblock 1.5.6 solved the problem for me.
I did not have GreaseMonkey but I *did* have AdBlock 0.7.5.5. Disabling AdBlock works around the problem and I can debug again. (Windows XP)
Okay, summarizing the replies so far:
Of those who were able to fix the problem: - 3 people reported that removing Adblock Plus fixed the problem. (2 Mac, 1 WinXP) - 2 people reported that rmoving Greasemonkey fixed the problem. (1 Mac, 1 WinXP) - 1 person reported that removing Google Toolbar fixed the problem. (WinVista) - 1 person reported that removing Flashblock fixed the problem. (OS unknown) There were two remaining people who were not able to fix the problem; neither of them has Greasemonkey. So what the heck can we learn from this? I am wondering if there is some general Firefox 3 bug in their extension support that breaks Flex Builder debugging. I am continuing to investigate. It seems to be related to which Firefox 3 add-ons I have enabled.
Enabling "IE Tab" add-on breaks debugging. When I disable it, debugging works fine. (No need to un-install it) Debugging works fine with the following add-ons (at least for me): Charles Autoconfiguration, Web Developer, Live HTTP Headers, Google Notebook, Foxmarks Bookmark Synchronizer. GUtil (2.3.2) and IE Tab (1.5.20080310) were the two extensions that break debugging.
Disabling both fixed the problem. AdBlock Plus 0.7.5.5 and Google Toolbar 3.1.20080605W disabled and the problem goes away for me .
WinXP and Firefox 3.0 (release) - first disabled Greasemonkey (as I read down the comments) and that didn't work, then I disabled AdBlock Plus which DID work. Out of interest I tried re-enabling just Greasemonkey and it stopped working again.
So possibly something about the way GM and AdBlock (and other plugins which when disabled seem to solve things for people) hook into the browser that conflicts with how the debug flash player hooks in. This does not occur in FireFox 3 release on OpenSuSE 10.3 (x86_64, but 32bit browser) with AdBlock 0.7.5.5 installed. I just stopped at a break point in a web-based Flex application and remembered this bug.
Tom, this isn't question of stoping on break points but the fact that the debug session doesn't even launch correctly, the browser just hands.
Something I did, after someone mentioning that a previous FF beta was still there after uninstall, was to check if I was in the same situation and it was true. There was a lingering FF 3 Beta that wasn't removed and Flex Builder was pointing to it, after deleting it and changed my browser preferences within Flex Builder, I'm able to debug again without a problem ( till now). I would advise people still not being able to debug with FF 3 Final, to check if they have also a previous FF 3 in their system and check if Flex Builder isn't trying to use that version instead. João - This is my first install of FF3. There was never any other version of FF3 (beta or RC) on the system I am having trouble with.
João Fernandes wrote:
> Tom, this isn't question of stoping on break points but the fact that the debug session doesn't even launch correctly, the browser just hangs. Actually that's not correct -- the symptom we're seeing is that the app runs just fine in the browser, but it doesn't connect properly to the debugger. That isn't spelled out in the "steps to reproduce," so I can understand the confusion, but that is the behavior we're seeing here at Adobe, and that's the behavior I have heard described by some other people as well. It sounds like the problem you were running into is a different one. But I'm glad you got it working! I am continuing to investigate. At this point we have quite a long list of extensions that, when installed, cause this problem; so I strongly suspect that the bug is not in the extensions themselves, but in either Firefox or the Flash player. I'll keep digging into it, but in the meantime, the workaround is clear: Either use a different browser, or disable your Firefox extensions. Thanks everyone for your help in tracking this down! NaP, should be easy to trace down, because it was fine in the RC to the best of my knowlege. I've been using the betas and RCs for ages, so am fairly sure I'd have noticed if debugging stop working.
Disabling IE Tab (1.5.20080310) and Adblock (0.5.3.043) resolved the issue for me.
My 2c. I have Firefox 3.0 on Windows XP with the following extensions:
Charles Autoconfiguration V3.2 Console2 V0.3.9.2 DownThemAll! V1.0.3 FireBug V1.2.0b3 Live HTTP Headers V0.14 PDF Download V1.0.1.2 User Agent Switcher V0.6.11 Web Developer V1.1.6 Debugging works fine - I have not seen the issue mentioned above. Hopefully this may help with debugging this issue. In the same vein...
I'm was previously running FF3bX (Minefield) and now I'm running FF3.0.1 (Gran Paradiso) with Flash 9.0r124 and the following extensions with no issue: * ChatZilla 0.9.83 * FireBug 1.2.0b3 * SQLite Manager 0.2.43 * WebDeveloper 1.1.6 I would suggest from reading the above comments that the potentially the problem is extensions that interfere with the rendering of the DOM. ie. before the page is displayed. I also have this problem.
What I don't understand is how inconsistent flex is when it terminates the debugger connection. I am using FF 3.0, Windows XP SP2 and Flex Builder 3. FF Addons: Firebug Web Developer Bar Greasemonkey If I launch one of my old projects, created before I installed FF3, the debugger works fine. Any new project created after I installed FF3 causes the debugger to terminate right as it launches. The debugger still terminated with Greasemonkey installed but disabled. I uninstalled Greasemonkey and now my new flex projects and old flex projects work with the debugger. It appears some addons in FF cause problems. Why old projects would work and new ones would not work I have no clue. At least uninstalling greasemonkey has fix the problem for now. The following extensions implement a content policy:
Adblock Adblock Plus GreaseMonkey NoScript IE Tab Google Toolbar And other than that these extensions have nothing in common. Content policies implemented in JavaScript are known to cause issues with plugins because they force the browser to make the plugin available to JavaScript before it is fully initialized. This is definitely one of those issues. Flashblock uses XBL rather than content policies, so that's a different issue. workaround: set wmode to opaque rather than window:
http://mostlyflex.com/2008/06/23/firefox3-vs-flex-builder/ very weird but it works for me. Logged against Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=441424
People who voted for this Flex Builder bug, please go to the above Firefox bug and vote for it.
That would be pointless, nobody cares about vote counts. Also, please don't add comments unless you have new technical details - "this affects me too" and "why don't you do anything" style comments don't help the bug getting resolved.
This seems to be an intermittent problem, not 100% reproducable. When I first installed Firefox 3 last week (about 7 days ago) my debugging in Flex Builder seemed to work fine with Firefox 3. Just today when doing some heavy debugging I noticed this issue popping up but was able to get debugging working again by trying a few times over. Now, at the end of the day, I am not able to get it working at all.
Diabling the Greasemonkey and AdBlock extensions seemed to fix it for me but I can't keep Greasemonkey disabled, it's far too useful. Same comment added to the FF bug. I'm having the same problems described. I also have Greasemonkey.
Here is a more general symptom of the problem I observed: If you look at the flash log file when playing in FF3 - and follow traces - You will see that the swf STARTS TWICE(!). Steps to reproduce: 1. Create a Flash/Flex swf that traces something. 2. Generate an HTML file showing it (using java script). 3. Run in browser 4. Open the trace log file Actual Results: 1. At a certain point in the execution of the swf, after the initial document class finishes instantiating and is waiting for events, the swf is starting a second time (thus breaking any debugger connection) 2. This only happens when using the java script embedding of the swf. With the embed/object tags it doesn't relapse. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bug
Resolved
A+
Firefox 3 and Flex Debug Not Working