Solution to startup failure caused by flash builder disabling illegally

Sometimes, for some reason, if Flash builder is disabled illegally (for example, crashed), an error will be prompted when Flash builder is started again, prompting you to view an inexplicable log.

It is really annoying to have such a problem. In fact, it is a problem left by ECLIPSE, rather than a flash builder, so we can solve it according to the eclipse solution.

Most of the suggestions on the Internet are to delete all files and directories under. metadata in the workspace. In this way, flash builder can be started smoothly, but the side effects are huge. Your settings and projects are all gone and you need to reset and import them. If there are many projects, it will cause you to crash directly, this method is a last resort.

This method will be better and has little side effects, that is, add the startup parameter "-clean" at startup ".

For example, we can start flash builder through cmd, as shown below:

Cd e:

CD flashbuilder

Flashbuilder.exe-clean

In this way, flash builder can be started smoothly, and all the projects and settings will not be lost. I personally think this is the best solution known.

This article from: http://www.richbox.net/blog? Cat = 4 & paged = 2