No more handles

Swing Designer allows you to quickly create the frames, panels, dialogs, applets and other UI elements that comprise Java Swing applications.

Moderators: Konstantin.Scheglov, gnebling, Alexander.Mitin, jwren, Eric Clayberg

No more handles

Postby doc » Mon Aug 10, 2009 4:36 am

Eclipse Platform
Version: 3.4.2
Build id: M20090211-1700


After intensive use of the swing designer I get the following exception (taken from log file):

Code: Select all
!ENTRY com.instantiations.designer.core 4 4 2009-08-10 14:18:54.089
!MESSAGE Designer [7.1.0.200907201341]: No more handles
!STACK 0
org.eclipse.swt.SWTError: No more handles
   at org.eclipse.swt.SWT.error(SWT.java:3803)
   at org.eclipse.swt.SWT.error(SWT.java:3695)
   at org.eclipse.swt.SWT.error(SWT.java:3666)
   at org.eclipse.swt.graphics.Image.getImageData(Image.java:1447)
   at com.instantiations.designer.swing.utils.SwingImageUtils.convertImage_AWT_to_SWT(SwingImageUtils.java:633)
   at com.instantiations.designer.swing.utils.SwingImageUtils.makeShots(SwingImageUtils.java:314)
   at com.instantiations.designer.swing.model.component.ComponentInfo.createShotImages(ComponentInfo.java:235)
   at com.instantiations.designer.swing.model.component.ComponentInfo.refresh_fetch(ComponentInfo.java:110)
   at com.instantiations.designer.swing.model.component.ContainerInfo.refresh_fetch(ContainerInfo.java:200)
   at com.instantiations.designer.core.model.ObjectInfo$4.run(ObjectInfo.java:391)
   at com.instantiations.designer.core.utils.execution.ExecutionUtils.runDesignTime(ExecutionUtils.java:87)
   at com.instantiations.designer.core.model.ObjectInfo.refresh(ObjectInfo.java:388)
   at com.instantiations.designer.core.editor.DesignPage.internal_refreshGEF_withProgress(DesignPage.java:443)
   at com.instantiations.designer.core.editor.DesignPage.access$800(DesignPage.java:57)
   at com.instantiations.designer.core.editor.DesignPage$7$1.run(DesignPage.java:316)
   at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:178)
   at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150)
   at org.eclipse.swt.widgets.Display.syncExec(Display.java:4251)
   at com.instantiations.designer.core.editor.DesignPage$7.run(DesignPage.java:313)
   at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
   at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
   at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
   at com.instantiations.designer.core.editor.DesignPage.internal_refreshGEF(DesignPage.java:334)
   at com.instantiations.designer.core.editor.UndoManager.refreshDesignerEditor(UndoManager.java:444)
   at com.instantiations.designer.core.editor.DesignPage.refreshGEF(DesignPage.java:292)
   at com.instantiations.designer.core.editor.actions.RefreshAction.run(RefreshAction.java:30)
   at com.instantiations.designer.core.editor.actions.DesignPageAction.run(DesignPageAction.java:23)
   at com.instantiations.designer.core.editor.errors.ExceptionComposite$2.widgetSelected(ExceptionComposite.java:97)
   at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
   at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
   at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
   at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
   at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
   at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384)
   at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348)
   at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200)
   at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495)
   at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
   at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490)
   at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
   at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
   at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
   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:386)
   at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
   at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
   at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
   at org.eclipse.equinox.launcher.Main.main(Main.java:1212)


Any further source code parsing fails. The only way to fix the problem is to restart eclipse.
doc
 
Posts: 14
Joined: Thu Jun 25, 2009 1:52 am

Re: No more handles

Postby Alexander.Mitin » Mon Aug 10, 2009 5:26 am

Which OS you are using?
Alexander Mitin
Alexander.Mitin
Moderator
 
Posts: 155
Joined: Fri Jan 19, 2007 3:57 am

Re: No more handles

Postby doc » Mon Aug 10, 2009 5:29 am

Windows XP SP2
doc
 
Posts: 14
Joined: Thu Jun 25, 2009 1:52 am

Re: No more handles

Postby Eric Clayberg » Mon Aug 10, 2009 6:16 am

Are you using an custom Swing widgets or just standard components?

How much memory do you have assigned to Eclipse?

When Eclipse throws an "No more handles" exception, restarting Eclipse is pretty much the only option.
Eric Clayberg
Software Engineering Manager
Google
http://code.google.com/webtoolkit/download.html

Author: "Eclipse Plug-ins"
http://www.qualityeclipse.com
Eric Clayberg
Moderator
 
Posts: 4503
Joined: Tue Sep 30, 2003 6:39 am
Location: Boston, MA USA

Re: No more handles

Postby doc » Mon Aug 10, 2009 6:55 am

Eclipse is starting with
-Xmx1536m -XX:MaxPermSize=128m

There is one custom swing widget in my dialogs which depends on a JComboBox.

The exception also occures while editing frames without the custom widget...
doc
 
Posts: 14
Joined: Thu Jun 25, 2009 1:52 am

Re: No more handles

Postby Eric Clayberg » Mon Aug 10, 2009 8:59 am

Unfortunately, that exception is a downstream side effect of something (or somethings) that happened earlier in the session (anywhere in Eclipse). It can be associated with custom widgets, but that is only one possible explanation.

If you create a new JFrame in a new session, and then start adding widgets and/or editing, are you able to reproduce this?
Eric Clayberg
Software Engineering Manager
Google
http://code.google.com/webtoolkit/download.html

Author: "Eclipse Plug-ins"
http://www.qualityeclipse.com
Eric Clayberg
Moderator
 
Posts: 4503
Joined: Tue Sep 30, 2003 6:39 am
Location: Boston, MA USA

Re: No more handles

Postby doc » Mon Aug 10, 2009 11:21 pm

No, the exception occurs usually after a few hours of editing, (re)parsing and designing of most diverse ui elements.
As far as I can see there is no possibility to derive a reproducible way of use.
doc
 
Posts: 14
Joined: Thu Jun 25, 2009 1:52 am

Re: No more handles

Postby Eric Clayberg » Thu Aug 13, 2009 7:07 am

If you have been editing in Eclipse for several hours, this could be a side effect of almost anything.

Assuming it is even Swing Designer related, we would need some sort of test case to reproduce it.
Eric Clayberg
Software Engineering Manager
Google
http://code.google.com/webtoolkit/download.html

Author: "Eclipse Plug-ins"
http://www.qualityeclipse.com
Eric Clayberg
Moderator
 
Posts: 4503
Joined: Tue Sep 30, 2003 6:39 am
Location: Boston, MA USA


Return to Swing Designer

Who is online

Users browsing this forum: No registered users and 1 guest