Community
Participate
Working Groups
Build Identifier: I20100520-1744 Environment: 1) dtp-sdk-1.8.0RC1-201005130500 2) eclipse-SDK-3.6RC2-win32 3) emf-xsd-SDK-2.6.0RC2 4) GEF-SDK-3.6.0M7 5) wtp-sdk-S-3.2.0RC2-20100520232028 But I think it will be reproducible under the latest version of this environment. 6) Java 1.5.18 7) Eclipse win32 8) Win XP SP1 x64 Edition Version 2003 Win XP SP1 x64 Edition Version 2003 Reproducible: Always Steps to Reproduce: 1. Extract attached archive and import all plug-ins to clear workspace 2. Run new configuration 3. Create dynamic web-project 4. Create any jsp, html page 5. Open this page with Visual Editor ("Visual Editor" is editor from attached plug-ins. It's only initialize SWT Mozilla Browser with xulrunner specified in org.mozilla.xulrunner.win32.win32.x86) As the result you can see smt. like this in your error log: java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: D:\WorkSpaces\heliosws\.metadata\.plugins\org.eclipse.pde.core\Test\org.eclipse.osgi\bundles\487\1\.cp\swt-xulrunner-win32-3649.dll: This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem no swt-xulrunner-win32 in java.library.path D:\Documents and Settings\Administrator.YZHISHKO\Local Settings\Temp\swtlib-32\swt-xulrunner-win32-3649.dll: This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem Can't load library: D:\DOCUME~1\ADMINI~1.YZH\LOCALS~1\Temp\swtlib-32\swt-xulrunner-win32.dll at org.eclipse.swt.internal.Library.loadLibrary(Library.java:267) at org.eclipse.swt.internal.Library.loadLibrary(Library.java:174) at org.eclipse.swt.browser.Mozilla.initXULRunner(Mozilla.java:2302) ... 45 more
Created attachment 171420 [details] Archive with plug-ins to be imported
This is likely bug 311936, which was ultimately fixed in 3.6RC3. Please try with the http://download.eclipse.org/eclipse/downloads/drops/S-3.6RC4-201006031500/index.php release and follow up here whether this helps.
Yep. It was fixed in CR3, CR4 version. Bug may be closed.
*** This bug has been marked as a duplicate of bug 311936 ***
(In reply to comment #4) > > *** This bug has been marked as a duplicate of bug 311936 *** Hello Guys, for x64 versions of - Eclipse Version: 3.6.0 RC4 - Build id: I20100603-1500 this bug still exists. The eclipse.ini points to a x64 version of XulRunner: -Dorg.eclipse.swt.browser.XULRunnerPath=C:\XulRunner\x64\ but I got the "same" error: org.eclipse.swt.SWTError: No more handles (java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: no swt-xulrunner-win32-3650 in java.library.path no swt-xulrunner-win32 in java.library.path Can't load library: C:\Users\KLOESS~1.FRI\AppData\Local\Temp\swtlib-64\swt-xulrunner-win32-3650.dll Can't load library: C:\Users\KLOESS~1.FRI\AppData\Local\Temp\swtlib-64\swt-xulrunner-win32.dll ) at org.eclipse.swt.SWT.error(SWT.java:4109) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.browser.Mozilla.initXULRunner(Mozilla.java:2304) at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:622) at org.eclipse.swt.browser.Browser.<init>(Browser.java:119) at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:94) at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:143) at org.jboss.tools.vpe.editor.mozilla.XulRunnerEditor2.<init>(XulRunnerEditor2.java:23) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:605) at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:886) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:222) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:434) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:166) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.java:271) at org.eclipse.ui.internal.EditorManager.setVisibleEditor(EditorManager.java:1429) at org.eclipse.ui.internal.EditorManager$5.runWithException(EditorManager.java:942) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$31.runWithException(Workbench.java:1566) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2537) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) Caused by: java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: no swt-xulrunner-win32-3650 in java.library.path no swt-xulrunner-win32 in java.library.path Can't load library: C:\Users\KLOESS~1.FRI\AppData\Local\Temp\swtlib-64\swt-xulrunner-win32-3650.dll Can't load library: C:\Users\KLOESS~1.FRI\AppData\Local\Temp\swtlib-64\swt-xulrunner-win32.dll at org.eclipse.swt.internal.Library.loadLibrary(Library.java:267) at org.eclipse.swt.internal.Library.loadLibrary(Library.java:174) at org.eclipse.swt.browser.Mozilla.initXULRunner(Mozilla.java:2302) ... 48 more What I did wrong? ;) Thanks, Steffen Thanks
re: comment 5 You're seeing something different, swt's 64-bit Windows port does not have xulrunner support because mozilla.org does not provide a 64-bit xulrunner on Windows. Where did you get yours from? The request for xulrunner support on 64-bit Windows is bug 199660.
(In reply to comment #6) > re: comment 5 > > You're seeing something different, swt's 64-bit Windows port does not have > xulrunner support because mozilla.org does not provide a 64-bit xulrunner on > Windows. Where did you get yours from? > > The request for xulrunner support on 64-bit Windows is bug 199660. hmm ... I found a 64 bit xulrunner for win64 here: http://wiki.mozilla-x86-64.com/Download
