For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 23 replies, 12 voices, and was last updated 20 years, 8 months ago by
Anup Chatterjee.
-
AuthorPosts
-
lzechmeiMemberAfter upgrading to 3.8.3 Create ER Diagram is OK, but export as jpeg activates a pop up: “Error exporting image”.
Trying again: “Reason: No more handles”.December 16, 2004 at 9:24 am #221311
Riyad KallaMember“No more handles” is an SWT/OS system level error that can occur. Check your log file (workspace dir)\.metadata\.log for more details to help us figure out what happened.
December 16, 2004 at 3:04 pm #221355
GregMemberLet us know about your system profile by using the “Insert” system profile button. Since the “No more handles” is a OS level error we need to know your OS, etc. The system profile will give us all that information.
December 17, 2004 at 4:14 am #221388
support-michaelKeymasterHow large is your ER (tables & rels)? I believe “no more handles” in this case is an indication that the SWT is unable to handle the image conversion due to its size. We are researching this issue.
December 17, 2004 at 4:32 am #221391
lzechmeiMemberSorry, I must still learn…
– System Setup ——————————-
Operating System and version: Windows 2000
Eclipse version: 3.0.1
Eclipse build id: 200409161125
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins: 0
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 7
MyEclipse version: 3.8.3
Eclipse JDK version: 1.4.2_04
Application Server JDK version: 1.4.2_04
Are there any exceptions in the Eclipse log file? yLOG:
!SESSION Dec 17, 2004 11:19:55.739 ———————————————
eclipse.buildId=M200409161125
java.version=1.4.2_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US!ENTRY com.genuitec.eclipse.sqlexplorer 4 4 Dec 17, 2004 11:19:55.759
!MESSAGE Error saving image
!STACK 0
org.eclipse.swt.SWTError: No more handles
at org.eclipse.swt.SWT.error(SWT.java:2717)
at org.eclipse.swt.graphics.Image.init(Image.java:1366)
at org.eclipse.swt.graphics.Image.<init>(Image.java:161)
at com.genuitec.eclipse.erdesigner.actions.ExportImageAction.run(Unknown Source)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:881)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:915)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:866)
at org.eclipse.jface.action.ActionContributionItem$7.handleEvent(ActionContributionItem.java:785)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2772)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2431)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1377)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:254)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:96)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:335)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
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.core.launcher.Main.basicRun(Main.java:185)
at org.eclipse.core.launcher.Main.run(Main.java:704)
at org.eclipse.core.launcher.Main.main(Main.java:688)!ENTRY org.eclipse.webbrowser 2 0 Dec 17, 2004 11:20:12.83
!MESSAGE Internal browser is not operational
!STACK 0
org.eclipse.swt.SWTError: No more handles
at org.eclipse.swt.SWT.error(SWT.java:2717)
at org.eclipse.swt.SWT.error(SWT.java:2616)
at org.eclipse.swt.SWT.error(SWT.java:2587)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:146)
at org.eclipse.webbrowser.internal.WebBrowserUtil.isInternalBrowserOperational(Unknown Source)
at org.eclipse.webbrowser.internal.BrowserManager.addInternalBrowser(Unknown Source)
at org.eclipse.webbrowser.internal.BrowserManager.loadBrowsers(Unknown Source)
at org.eclipse.webbrowser.internal.BrowserManager.getWebBrowsers(Unknown Source)
at org.eclipse.webbrowser.internal.WebBrowserUIPlugin.stop(Unknown Source)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:994)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:990)
at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:502)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.stop(AbstractBundle.java:437)
at org.eclipse.core.runtime.adaptor.BundleStopper.basicStopBundles(BundleStopper.java:73)
at org.eclipse.core.runtime.adaptor.BundleStopper.stopBundles(BundleStopper.java:62)
at org.eclipse.core.runtime.adaptor.EclipseAdaptor.frameworkStopping(EclipseAdaptor.java:551)
at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:457)
at org.eclipse.osgi.framework.internal.core.SystemBundle$1.run(SystemBundle.java:182)
at java.lang.Thread.run(Unknown Source)!ENTRY org.eclipse.webbrowser 1 0 Dec 17, 2004 11:20:12.83
!MESSAGE true/false– Message Body ——————————-
I hope it helps:
number of Tables: 36
number of References: 103
(Remark: I do not need the printing feature immediately.)December 17, 2004 at 7:32 am #221395
Riyad KallaMemberThis problem alawys seems to be tied into a malfunction with the browser widget… very strange.
What is your system’s default browser? If you have mozilla installed, can you try reinstalling Mozilla 1.6 instead of 1.7+ and see if that fixes it? (it works under Linux)
December 17, 2004 at 8:01 am #221398
Brian FernandesModeratorI’m not sure about the browser widget being a problem … but here is the scoop on the SWT no more handles.
The internal bitmaps that are used to store the image have a limit on size. ie. they can only be a maximum of 16 MB. This was supposed to be a limitation on only Windows 95 / 98 / ME – but I think a similar limitation might exist with 2000 and XP as well. I have an XP system myself and I have similar problems. If your image is going to occupy more than 16 MB – it won’t work this time around, sorry. Linux exports are obviously not affected by this issue and I’ve seen large diagrams being exported w/o problem.
You can calucate the bitmap memory requirement by using something like width x height x bpp / 8 (bpp = bits per pixel, usually 16, 24 or 32 – check your screen depth)
Sorry about the limitation atm – it will be removed in the next release.
Thanks,
Brian.December 20, 2004 at 12:51 am #221549
lzechmeiMemberBrowser: IE 5.50
Image size sounds plaisible, the picture is rather big (but it is a real project with real size).As mentioned earlier, the matter is not urgent. I wanted simply to help you eliminating a bug.
January 20, 2005 at 3:51 pm #223254
mstrong4867MemberI’m having the same problem.
Did you ever resolve this one?
January 20, 2005 at 4:19 pm #223258
Riyad KallaMemberThis didn’t make it into 3.8.4 unfortunately.
February 8, 2005 at 10:22 am #224690
tibiParticipantyes i have the same problem. at the beginning i could get arround it when i moved al the object close together 😳 but now it does not fit any more . 🙁
when will it be fixed?
February 8, 2005 at 10:26 am #224691
tibiParticipanti would be happy with a work arround of getting two half images
February 8, 2005 at 10:41 am #224696
tibiParticipantone more thing when you get the error it seems to persist even when the image gets smaller. you will notic that the error message apears quite fast. when you restart eclipse and made your image small enough it could all work again. (in my case!)
March 3, 2005 at 3:47 pm #226129
sm_vaidMemberI experienced this problem also, and just to confirm that it was resolved by re-saving the image with a smaller color depth. I did this by reducing the color depth to 16 bit in the Windows display properties.
😯
March 6, 2005 at 12:57 am #226229
Brian FernandesModeratorYour 16 bit trick is a good one 🙂
A 16 bit image would take half the space of a 32 bit image, so you can get away with larger images…We hope to fix this problem soon – sorry for the inconvenience caused.
Brian. -
AuthorPosts
