Tagged: MOZILLA SWTError x86_64
December 2, 2017 at 11:11 am #544397
I just update MyEclipse to 2017 CI 9 and the log show this error:1234org.eclipse.swt.SWTError: No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)]at org.eclipse.swt.SWT.error(SWT.java:4559)at org.eclipse.swt.browser.Mozilla.initMozilla(Mozilla.java:2237)at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:691)
The application is running on Arch Linux x86_64.
How to solve this problem ?
This problem happen with GTK2 configuration only. It work fine with GTK3 but still have problem with graphic item position with this configuration.
ThanksDecember 3, 2017 at 3:23 am #544409
After downloading XulRunner 22.214.171.124 and adding the following option to myeclipse.ini
the log files shows the following messages123456789101112131415161718192021eclipse.buildId=15.0.1.CI-009java.version=1.8.0_112java.vendor=Oracle CorporationBootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_USCommand-line arguments: -os linux -ws gtk -arch x86_64...!ENTRY org.eclipse.jface 2 0 2017-12-03 10:21:08.634!MESSAGE Ignored labelProviderChanged notification because control is diposed. This indicates a potential memory leak. This is only logged once per viewer instance, but similar calls will still be ignored.!STACK 0java.lang.RuntimeExceptionat org.eclipse.jface.viewers.ContentViewer$1.labelProviderChanged(ContentViewer.java:95)at org.eclipse.jface.viewers.BaseLabelProvider$1.run(BaseLabelProvider.java:72)...!ENTRY org.eclipse.osgi 4 0 2017-12-03 10:21:08.657!MESSAGE Application error!STACK 1org.eclipse.swt.SWTError: XPCOM error 0x80004005at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:2966)...
Creating a new workspace works fine. Re-opening the new one generate the same problem.
December 3, 2017 at 3:20 pm #544420
- This reply was modified 1 year, 1 month ago by Sylvain Bonnemaison.
I have tested with xulrunner version 1.9.2 (x86), 126.96.36.199 (x86), 2.0 (x86_64), 36.0.4 (x86_64) and 41.0.2 (x86_64) with a small difference in the result :123456789101112131415161718...!ENTRY org.eclipse.e4.ui.workbench 4 0 2017-12-03 22:12:57.075!MESSAGE Exception occurred while rendering: org.eclipse.e4.ui.model.application.ui.advanced.impl.PlaceholderImpl@3119fcad (elementId: org.eclipse.ui.views.ProblemView, tags: , contributorURI: null) (widget: null, renderer: org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer@4c14b1bd, toBeRendered: true, onTop: false, visible: true, containerData: null, accessibilityPhrase: null) (closeable: false)!STACK 0java.lang.IllegalArgumentException: Argument cannot be nullat org.eclipse.swt.SWT.error(SWT.java:4514)...!ENTRY org.eclipse.jface 2 0 2017-12-03 22:12:57.363!MESSAGE Ignored labelProviderChanged notification because control is diposed. This indicates a potential memory leak. This is only logged once per viewer instance, but similar calls will still be ignored.!STACK 0java.lang.RuntimeExceptionat org.eclipse.jface.viewers.ContentViewer$1.labelProviderChanged(ContentViewer.java:95)...!ENTRY org.eclipse.osgi 4 0 2017-12-03 22:12:57.389!MESSAGE Application error!STACK 1org.eclipse.swt.SWTError: XPCOM error 0x80004002at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:2966)
There is not such behavior with Eclipse Oxygen.
December 4, 2017 at 10:35 am #544464
- This reply was modified 1 year, 1 month ago by Sylvain Bonnemaison.
Sorry that you are seeing this issue. Thank you for the detailed info. We could replicate the problem at our end and the dev team is looking into it. We will keep you posted about the fix details.
Thank you for reporting it. Apologies for inconvenience caused.
MyEclipse SupportDecember 14, 2017 at 2:22 pm #545115
Any fix yet to solve the problem ?
I can’t use the IDE since more 10 days.December 15, 2017 at 3:37 am #545150
Apologies for the delay as we tried to replicate the issue and figure a workaround.
Fortunately, we’ve managed to see the issue with a version of Arch Linux (Anarchy linux), though only when the webkit2gtk package was not installed. Could you check that you have that package installed? If not please install it and check with GTK2.
If you have the package installed and are still seeing the issue, could you please let us know how you are switching MyEclipse to using GTK2? You can either set the environment variable SWT_GTK3=0 before starting MyEclipse:
SWT_GTK3=0 [path to MyEclipse install]/myeclipse
or by adding the following two lines, above the vmargs, to myeclipse.ini:12--launcher.GTK_version2
Also, if you continue getting the error, please let us know the windows manager/desktop environment you’re using to help us replicate.
Either way, please let us know how you get on.December 15, 2017 at 8:06 pm #545261
“webkit2gtk-2.18.3-3” is already installed on the system.
The configuration is using de vmargs in myeclipse.ini.
The system is running Gnome 3.26.2.
That’s disappointing. I have the same versions of webkit2gtk and gnome but don’t see an issue with GTK 2, although I do see the “no more handles” problem with GTK 3 when trying to shift views around the workbench.
For some eclipse users who’ve seen this, sometimes using a different JDK has solved the issue. As I can’t replicate the problem, I don’t know if that will work in this case but you can try commenting out the -vm and following lines in your myeclipse.ini file, so that the system installed JDK is picked up, and this will replicate what Oxygen is picking up also (you mentioned that you don’t see the issue with Oxygen).
If you still see the issue, could you let us know exactly when the error occurs (that is, what you are doing at the time the error occurs) and attach your myeclipse.ini file to help us replicate your setup. Also, since you don’t see it with Oxygen, could you try with a Neon install, to check if it’s a problem that got fixed in Oxygen.
Something else occurs to me. Your opening post suggests that you were running with MyEclipse CI 8 without a problem. If this is so, you can revert to CI 8 and, hopefully, get up and running. Go to Help->Check for Updates. The resulting dialog should show no updates but will also give you the option of locking to CI 8. Just click the Lock button and then OK, to have the installation revert to CI 8.
Please let us know how you get on and sorry for the continuing problems.December 20, 2017 at 4:14 pm #545578
I still have the same problem by reverting to version CI8. Even using a different JDK.
See attached MyEclipse configuration file.December 20, 2017 at 4:15 pm #545579
Here is the configuration file content:123456789101112131415161718192021222324#ansi (do not remove)-startupplugins/org.eclipse.equinox.launcher_1.3.200.v20160318-1642.jar--launcher.libraryplugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.400.v20160518-1444--launcher.GTK_version2--launcher.defaultActionopenFile-vm/opt/jdk1.8.0_151/bin/java-configuration/opt/myeclipse-2017/configuration-install/home/workspace-vmargs-Xms256m-Xmx1024m-XX:+UseG1GC-XX:+UseStringDeduplication-Dosgi.requiredJavaVersion=1.8-Dosgi.nls.warnings=ignore-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-41.0.2/-Dorg.eclipse.swt.browser.UseWebKitGTK=trueDecember 20, 2017 at 4:37 pm #545580
Thanks for those pieces of information.
So, to be clear, are you saying that you didn’t see the problem with CI 8 but after updating to CI 9 you did see the problem, but now, after reverting to CI 8, you still see the problem? Is that right?
You may need to launch MyEclipse once with the -clean flag to ensure the plug-in cache is cleared after reverting to CI 8. You can do this by launching myeclipse from the command line and adding the flag, such as:
Please also check my previous reply for suggestions about trying eclipse neon and asking for details on when the problem occurs. Additionally, you can try downloading and installing the older 2017 Stable 1.0 release (which can be downloaded from our site), which would give you a cleaner MyEclipse install without the updates (though it is a much older release).December 20, 2017 at 5:04 pm #545581
Running from the console :
I get the following error message :1234567891011121314org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.org.eclipse.m2e.logback.configuration: Logback config file: /home/sbonnema/Workspaces/MyEclipse 2017 CI/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.188.8.131.5260603-1933.xmlSLF4J: Class path contains multiple SLF4J bindings.SLF4J: Found binding in [bundleresource://1416.fwk1555690610:1/org/slf4j/impl/StaticLoggerBinder.class]SLF4J: Found binding in [bundleresource://1416.fwk1555690610:2/org/slf4j/impl/StaticLoggerBinder.class]SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]org.eclipse.m2e.logback.configuration: Initializing logback## A fatal error has been detected by the Java Runtime Environment:## SIGSEGV (0xb) at pc=0x0000000000000000, pid=30486, tid=0x00007f2bd4244700...
with the attached error log file.
The IDE start with a new blank workspace.
- This reply was modified 1 year ago by Sylvain Bonnemaison.
Attachments:You must be logged in to view attached files.December 22, 2017 at 12:10 am #545644
Sorry for the delay in responding (we had some internal technical issues).
It’s disappointing that the clean didn’t help. I’ve now checked with both Gnome and Mate desktop manager in an install of Antergos (a derivative of Arch Linux). I do see the issue with Mate and did get some initial problems with Gnome (though not the problem you see). However, in the case of Mate, using GTK2 and the UseWebKitGTK property did solve the issue after a settings change though the NO_MORE_HANDLES issue did appear when trying to open an internal browser but that didn’t affect further use of the IDE. With Gnome, I didn’t see that issue at all. Installing xulrunner and setting the xulrunner path property did cause much more problems. So, I have the following questions and suggestions:
- Which window manager are you using (for example, Gnome, KDE, Mate)?
- If you aren’t able set the option on the MyEclipse dashboard to prevent its showing up in subsequent launches, add the following line to the com.genuitec.eclipse.dashboard.prefs file, found in the .metadata/.plugins/org.eclipse.core.runtime/.settings folder of your workspace:
With Mate, it is the attempt to open this view that is causing the NO_MORE_HANDLES issue for me.
- Remove the xulrunner path property from your myeclipse.ini file
- Start with a fresh workspace and see if the above settings work.
- If you still see the issue, when does it occur and how does it affect other use of the IDE?
- Which release of MyEclipse were you using before updating to CI 9 and started to see the problem?
Please try to answer all questions, if the suggestions don’t help; they will help us investigate it further. However, this sort of issue is related to underlying problems with the eclipse base, so we may not be able to provide a solution until MyEclipse 2018, which will be based on eclipse Oxygen, which you wrote doesn’t show the problem.