• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
Locked
0

flashbuilder has stopped working

Participant ,
Apr 06, 2012 Apr 06, 2012

Copy link to clipboard

Copied

Last night I was using flashbuilder; then went I went to bed I started encoding with Media Encoder; when I woke up this morning my computer (winXP) was turned off; now flashbuilder will not start.

Here is a log generated from double-clicking the flashbuilder icon on my desktop:

!SESSION 2012-04-06 18:46:50.984 -----------------------------------------------

eclipse.buildId=M20100909-0800

java.version=1.6.0_16

java.vendor=Sun Microsystems Inc.

BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.osgi 4 0 2012-04-06 18:46:53.062

!MESSAGE Application error

!STACK 1

org.eclipse.swt.SWTError: No more handles

    at org.eclipse.swt.SWT.error(SWT.java:4109)

    at org.eclipse.swt.SWT.error(SWT.java:3998)

    at org.eclipse.swt.SWT.error(SWT.java:3969)

    at org.eclipse.swt.widgets.Widget.error(Widget.java:468)

    at org.eclipse.swt.widgets.Control.createHandle(Control.java:633)

    at org.eclipse.swt.widgets.Composite.createHandle(Composite.java:305)

    at org.eclipse.swt.widgets.Control.createWidget(Control.java:649)

    at org.eclipse.swt.widgets.Scrollable.createWidget(Scrollable.java:134)

    at org.eclipse.swt.widgets.Control.<init>(Control.java:110)

    at org.eclipse.swt.widgets.Scrollable.<init>(Scrollable.java:75)

    at org.eclipse.swt.widgets.Composite.<init>(Composite.java:95)

    at org.eclipse.ui.splash.BasicSplashHandler.getBundleProgressMonitor(BasicSplashHandler.java:159)

    at org.eclipse.ui.splash.BasicSplashHandler.getContent(BasicSplashHandler.java:265)

    at org.eclipse.ui.internal.splash.EclipseSplashHandler.init(EclipseSplashHandler.java:86)

    at org.eclipse.ui.internal.Workbench$8.run(Workbench.java:782)

    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

    at org.eclipse.ui.internal.Workbench.createSplashWrapper(Workbench.java:798)

    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2467)

    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)

    at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)

    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)

    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)

    at com.adobe.flexbuilder.standalone.FlashBuilderApplication.start(FlashBuilderApplication.java:108)

    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)

    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)

    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)

    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

    at java.lang.reflect.Method.invoke(Unknown Source)

    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)

    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)

    at org.eclipse.equinox.launcher.Main.run(Main.java:1407)

any ideas?

thanks

Views

1.8K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Participant , Apr 07, 2012 Apr 07, 2012

Jon, thanks for responding ...


I 'fixed' it last night (2AM)

FIRST: I tried re-installing flashbuilder, but without uninstalling first ... did not work

SECOND: I used winxp add/remove programs to uninstall flashbuilder, then I re-installed flashbuilder ... worked

I should note that my eclipse was working all the while. I know that they are separate softwares, but nevertheless I figured that I would mention it.

Also, because my flashbuilder is basically out-of-the-box new, un-installing was acceptabl

...

Votes

Translate

Translate
Contributor ,
Apr 07, 2012 Apr 07, 2012

Copy link to clipboard

Copied

Check post #7 here:

http://forums.adobe.com/message/4044057#4044057

Also, this looks like a generic Eclipse bug, not only Flash Builder. So googling

eclipse "no more handles"

may yield more relevant results.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Apr 07, 2012 Apr 07, 2012

Copy link to clipboard

Copied

Jon, thanks for responding ...


I 'fixed' it last night (2AM)

FIRST: I tried re-installing flashbuilder, but without uninstalling first ... did not work

SECOND: I used winxp add/remove programs to uninstall flashbuilder, then I re-installed flashbuilder ... worked

I should note that my eclipse was working all the while. I know that they are separate softwares, but nevertheless I figured that I would mention it.

Also, because my flashbuilder is basically out-of-the-box new, un-installing was acceptable. But for someone who has added plugins, or done some customized configurations to their flashbuilder, un-installing would NOT be a good idea.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Apr 07, 2012 Apr 07, 2012

Copy link to clipboard

Copied

LATEST

Unless FB has been installed into an existing Eclipse installation they are seperate installs. So one Eclipse may be working, but FB's may not. A reinstall often fixes the problem, but is rather a sledgehammer approach. Often simply rebuilding a workspace or removing temporary files will help.

Anyway, glad you fixed it.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines