Today I had a similar problem to the one in this post – but instead of hanging, Flash Builder just failed to start up and quit during the “loading workbench” phase of initialization.
In the earlier post, I mentioned deleting a .snap file in [workspacelocation]/.metadata/.plugins/org.eclipse.core.resources, but previously I hadn’t been able to find it. This time, there WAS a .snap file in that folder, but it was hidden.
Deleted it, and Flash Builder starts up like a champ.
According to this thread, Flash Builder will only notice when your library SWC changes if it’s in your project folder. Kind of sucks if you use the same SWC in multiple projects, like I do, but it appears to be the only option. Also, sometimes you need to clean the project to make the refresh happen.
Now, I’m not using the Flex framework, but also from the linked thread, if you use Flex you might be able to turn off a “global SWC cache.” I tried it for my plain-jane actionscript projects and it didn’t work.
Here’s the secondary method:
Find the .options file in the /Applications/Adobe Flash Builder 4.7/eclipse/plugins/com.adobe.flexbuilder.project_4.7.0.349722/ folder and look for a line like this:
# use a global swc cache across all projects when compiling with flex sdk 4 or higher com.adobe.flexbuilder.project/useGlobalSwcCache=true
Try setting useGlobalSwcCache to false then restart Flash Builder and see if that helps.
NOTE: This may result in longer compile times in Flash Builder if your workspace includes Flash Library Projects since those generated SWCs will no longer be cached and instead will be rebuilt every time.
Again, I tried this secondary option, but it didn’t work for me (OSX 10.10.3 Yosemite), possibly because I don’t actually use Flex, and the comment in the config file specifically mentions Flex SDK.
Today Flash Builder randomly started hanging while loading the workbench on startup.
I found a lot of places that said to delete the .snap directory located at [workspacelocation]/.metadata/.plugins/org.eclipse.core.resources but there was never a .snap file or folder.
Eventually I found a trick here that said the following:
remove all the <editor> elements in workspace\.metadata\.plugins\org.eclipse.ui.workbench\workbench.xml
I did that and at least got Flash Builder to start up.
You apparently can also delete all the files in the [workspacelocation]/.metadata/.plugins/org.eclipse.ui.workbench as well (this removes your custom window layouts), but I haven’t tried this method.
As a last-ditch effort, you could do one of the following:
.metadata folder in your workspace folder. You will have to reimport ALL your projects after doing this.This happens because the Eclipse workspace gets corrupted. The easiest way I've found to recover from this is as follows: 1. Use Windows Task Manager (Ctrl+Shift+Esc) to make sure FlashBuilder.exe isn't running as a process. End the process if it is. 2. Navigate to your workspace folder (the default location is under your users folder in "Adobe Flash Builder 4.5", though you may have placed is elsewhere). Mine is c:\Users\grayson\Adobe Flash Builder 4.5 3. There is a folder named .metadata (on Windows 7 there is an issue where it may appear as a nameless folder because Windows started truncating the "extension") move it to another location on your hard drive. 4. Launch Flash Builder to make sure that this it has solved the issue. 5. Close Flash Builder (this writes the default workspace settings to the .metadata folder in your workspace location) Inside the original copy of the .metadata folder you made, COPY the following folders to the same location in the newly created .metadata folder in your workspace folder, overwriting the files and folders that are there. .metadata\.plugins\org.eclipse.core.resources\ .metadata\.plugins\org.eclipse.core.runtime\ (as I mentioned before, Windows 7 can truncate the folder names to be without the last portion of the name, so you may see two folders that appear to be named "org.eclipse.core.runtime". Copying them will still work) 6. This will restore the projects, workspace settings, and key bindings. (the dialog/window layout will be reset to the defaults and External Tool Configurations aren't copied. I looked but didn't find where those are stored)
This one’s a weird one. Sometimes Flash Builder 4.7 has a problem where weird errors come up in library code (Feathers, usually) that doesn’t have any actual errors in it.
The error raised is the following: com.google.common.collect.ComputationException: java.lang.NullPointerException
The (non-obvious) solution is to find a little button called “Mark Occurrences” in the toolbar and turn it to OFF.
Here’s a picture of what the button looks like when set to OFF:
And here’s what it looks like when set to ON:
Oh, and sometimes restarting Flash Builder doesn’t do it, so sometimes in order to fix it, I have to set mark occurrences to ON, close and restart FB, and then set it to OFF again to get it to work.
More info is available in this post in the Feathers forum here.
Situation: I’m making an app for iOS and Android using Flash Builder 4.7 and AIR SDK 4.0. It includes the Lua 5.2 interpreter as compiled from C code into a SWC using CrossBridge (formerly FlasCC). I’m just using the lua.swc file from the crossbridge samples. However, apparently there’s some problem with the multithreading code or something (is multithreading even supported in AIR 4.0? I don’t remember), because I get the following run-time error when debugging on the device (not on Android or AIR simulator, just iOS):
Error #1520: Mutex cannot be initialized.
Solution: I don’t know why this works, but if you add the following compiler options:
--swf-version=17
It works. This probably means I’m targeting an older flash player and one day I will need to figure out how to get the Lua interpreter code.
Here’s a pretty picture of the box where you enter the code in Flash Builder 4.7:
