[dombat]

Hi
After a fresh install of eclipse 3.0.1 and myeclipse 3.8.3 on an xp machine with Firefox 1.0 as default browser, I get in the .log file :

!SESSION déc. 14, 2004 12:24:52.343 ——————————————–
eclipse.buildId=M200409161125
java.version=1.4.2_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR
Command-line arguments: –vmargs –Xms128M –Xmx256M

!ENTRY org.eclipse.webbrowser 2 0 déc. 14, 2004 12:24:52.343
!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(Thread.java:534)

!ENTRY org.eclipse.webbrowser 1 0 déc. 14, 2004 12:24:52.343
!MESSAGE true/false

Dom

[Riyad Kalla]

Dom,
Thank you for posting all your info; can you tell us what it is you do when you get this error? We’ve started to see this “No more handles” issue when the browser on the platform is not compatible with the SWT Browser widget… on Windows the default was IE for the longest time but now that Firefox is gaining ground I think the SWT widget is having some growing pains. Please let us know what is going on and I’ll ask a dev to take a look at this for you.

[Scott Anderson]

If you attempt to open the MyEclipse Browser View or click on the Browser button in the toolbar (looks like a little globe) does the browser window open? Ist if functional?

[dombat]

Hi scott
This errors happens while loading eclipse, and as you can see, it happens once of two times!
Once eclipse is loaded, if internal browser has been selected, clicking on the map, the internal browser is displayed normaly.
if external Firefox has been selected, Firefox is loaded normaly.
No error is in .log

In the following log, I’ve loaded eclipse with the -clean option, 2 times : at 15:50:08 and 15:55:25
Then loaded eclipse without -clean at 15:56:08 and 15:58:14

Also note “org.eclipse.webbrowser 1 0” and “org.eclipse.webbrowser 2 0”

!SESSION déc. 20, 2004 15:50:08.593 ——————————————–
eclipse.buildId=M200409161125
java.version=1.4.2_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR
Command-line arguments: –vmargs –Xms128M –Xmx256M

!ENTRY org.eclipse.webbrowser 1 0 déc. 20, 2004 15:50:08.593
!MESSAGE true/true
!SESSION déc. 20, 2004 15:55:24.234 ——————————————–
eclipse.buildId=M200409161125
java.version=1.4.2_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR
Command-line arguments: –vmargs –Xms128M –Xmx256M

!ENTRY org.eclipse.webbrowser 2 0 déc. 20, 2004 15:55:24.234
!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(Thread.java:534)

!ENTRY org.eclipse.webbrowser 1 0 déc. 20, 2004 15:55:24.234
!MESSAGE true/false
!SESSION déc. 20, 2004 15:56:08.921 ——————————————–
eclipse.buildId=M200409161125
java.version=1.4.2_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR
Command-line arguments: –vmargs –Xms128M –Xmx256M

!ENTRY org.eclipse.webbrowser 1 0 déc. 20, 2004 15:56:08.921
!MESSAGE true/true
!SESSION déc. 20, 2004 15:58:14.406 ——————————————–
eclipse.buildId=M200409161125
java.version=1.4.2_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR
Command-line arguments: –vmargs –Xms128M –Xmx256M

!ENTRY org.eclipse.webbrowser 2 0 déc. 20, 2004 15:58:14.406
!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(Thread.java:534)

!ENTRY org.eclipse.webbrowser 1 0 déc. 20, 2004 15:58:14.406
!MESSAGE true/false

[Scott Anderson]

Dom,

From the stacktraces, these errors occur during shutdown of the workbench, not during startup. They are likely caused by portions of the framework being stopped before other portions that depend on them. This causes an error condition, but isn’t really of concern. We’ll enter a bug report to work around the problem in the future, but it seems that the message can be safely ignored since it doesn’t impact functionality.

[jkurtz_wa]

Moderator:

Any bug throwing errors should be a concern, even if in some cases overall functionality is not compromise.

These bugs are causing Eclipse to crash on my Linux box, so there is a concern afterall.

[Scott Anderson]

Yes, there is a concern and we investigated it with very high priority. The issue has been identified and addressed and we will provide a fix in 3.8.4 shortly.

[Author]

Posts