This content has been marked as final. Show 17 replies
I have Windows Vista Ultimate Retail and never had any issues.
Download latest Eclipse and try FB plugin with the latest JRE. If this still makes issues... I might say the problem is in your Vista or some other software installed.
Try disabling the enhanced graphic features (Aero) in Vista, I found them quite unstable on lots of installed software.
Thank you for your reply.
My machine is a clean install. I have Adobe Photoshop CS3, Flash CS3 VS.NET 2005, Flex Builder 2.01 and now FB 3.0 beta.
My point really is that there are issues. FB 3.0 is unusable. Adobe needs to look into it. FB 2.01 works just fine.
To help us learn more about your problem, can you send us your JVM crash log? This should be a *.log file located in the same directory as your flexbuilder.exe (or eclipse.exe) file.
In the meantime, you may want to try installing the FB beta as a plugin to Eclipse 3.3 -- this new version of Eclipse has a number of Vista-specific fixes.
This is how i usually get it to crash on me. Debug session i see what variable or node i need to look at in the debug variable area, i then type it in then save and everything freezes while debugging.
There are a bunch hr_err_xxx.log files in the FlexBuilder 3 folder. How would I send them to you?
I find the killing the process ieuser.exe each time after starting a debug session solves the problem 100% of the time. I can kill the process soon after starting a debug session or just before I close the browser window. If I don't then the next time I start a debug session the IDE will simply vanish leaving behind the a dialog with the error message listed earlier.
Will the next beta fix this issue?
Based on a previous thread I assume you are running on Eclipse 3.3. If so could you file a bug? You will be able to attach the log to the bug. Otherwise, can you try on Eclipse 3.3 and file a bug if it reproduces?
eclipse 3.3 install info
eclipse 3.3 download
Flex Builder plug in install instructions
Read prior to filing:
I have experienced the same issues with stability on Vista. Sometimes it crashes during compilation, othertimes during debugging. I have also noticed that if I leave an application suspended in the debugger for more than 20-30 seconds that on most occassions Eclipse locks up (watch cursor, nothing responds) completely and I have to kill it. I'm currently using Eclipse 3.2.2 so I will try Eclipse 3.3 to see if that helps.
The cause of your second problem (not being able to debug again after ending the first debug session) is due to the new protected mode under which IE 7 operates in Windows Vista. See http://msdn2.microsoft.com/en-us/library/Bb250462.aspx for details. Basically, after you terminate IE it leaves behind an ieuser.exe process and you need to kill this before you can launch another debug session.
I am not sure why, but this problem does not always occur. If the first use of IE after a reboot is a (debug?) session launched from Flex Builder, then I do not have to kill ieuser.exe. Well, at least for a while. At some point in stops working again. (I think if you close the browser while it is still running in debugger).
There are a number of separate Vista-related issues here:
* Eclipse has several bugs that cause crashes when running on Vista. One of these ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=161533 ) was fixed in Eclipse 3.2.2. If you're running Eclipse 3.2.1 (and that includes the last Flex Builder 3.0 beta, if you installed "standalone" instead of installing the Flex Builder plugins into your own Eclipse installation), then you will see this crash. The crash seems to be related to redrawing the tree control on Vista -- for example, when you begin or end a debugging session, the Debug panel's tree control redraws, and that can cause the crash. But it can happen when any tree control redraws, not just one of the debugging-related ones. I have seen this crash a lot; until the next beta of Flex Builder comes out, I recommend installing Eclipse 3.2.2 or 3.3, and then instaling the "plugin" version of Flex Builder into it, to avoid this problem.
* There is another occasional Eclipse crash which seems to still not be fixed by the Eclipse team, even on 3.3 ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=164389 ). I don't see this one very often, but I have seen it occasionally.
* The issue about not being able to debug a second time is, as dnbonnell says, caused by changes in IE's security model. We are working on a fix for this issue; in the meantime, the workaround, as Shiv says, is to manually kill ieuser.exe.
I hope that helps! - Mike Morearty, Flex Builder team
I just now finally figured out a workaround for the occasional problem when using Flex Builder on Vista, where Flex Builder tells you that another debugger is already running.
The workaround is to add this line to flexbuilder.ini or eclipse.ini (the name of the ini file depends on whether you installed standalone Flex Builder or the Eclipse plugin version of Flex Builder):
That's it. I suspect a bug in Vista -- the first time you debug, I can clearly see that Flex Builder is closing the socket, but when I run TCPView, it shows that the IPv6 version of the socket is still open, and that causes the problem. Adding the above property definition causes Java to only use IPv4.
Thanks for the update. Does the FB3 Beta 2 use the newer Eclipse IDE?
If not will the release version of FB3 be using the newer version of Eclipse?
didnt have time to read through all of above so sorry if this has already been said.
i solved almost all of my flex3B2 vista64 problems by installing eclipse 3.4M2
working a dream now. (had a shed load of troubles before)
hope this is of some help
I just installed FB3 Beta 2 and I don't have the crashing issues I used to have with Beta 1. I've not changed any settings nor have I made the change to the ini file as Mike suggested.
So it looks like it was an FB3 Beta 1 issue and not an Eclipse issue after all.
Yes, FB3 Beta 2 does use the newer Eclipse IDE (Eclipse 3.3).
Thanks for the heads up. That good news! That's probably why the crash issue is no longer present then huh?
it is working with 3.3 eclipse.
By the way Mike the new IDE does not crash on VISTA but unfortunately it does not debug more than once either.
Once again, killing the ieuser process fixes this issue. So I'll try your ini file fix and see what happens.
I can confirm that modifying the ini file as you've shown does work for me. I modified the FlexBuilder.ini file in my case and the debugging issue is gone.