My question is a bit like unexplored's.
My enviroment:
OS: windows server 2008 r2 (x64)
Safari installed 5.1.7
32 bit SWT (eclipse SDK 3.7.2 * 32)
32 bit jvm (32)
Add -Dorg.eclipse.swt.browser.DefaultType=webkit in eclipse.ini
Add C:\Program Files(x86)\Safari\Apple Application Support in windows PATH
Code like this:
//create Mozilla browser
browser = new Browser(parent, SWT.WEBKIT); //error was caused here.
Error message:
Unhandled event loop exception
No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]
With the same configuration,when my os is win7 - 32bit,it works well.
Anybody know why,or tell me how to find the cause?
Thanks very much
Related
EasyPHP-devserver-17.0 throws this error when starting the dashboard (win 7 x64):
Problem is I installed the 3 C++ redistributables they list: http://www.easyphp.org/faq_devserver.php#collapse001
first x64
then x64 + x86
then removed everything, installed only x86
then added x64 back
Still get the same error.
How can I fix it or get more info about what exactly is failing?
Since my computer has been updated to Mojave (macOS), I get the following error when I am trying to execute an Xtext project (Run As -> Eclipse Application):
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x00007fff51115248, pid=10464, tid=775
JRE version: Java(TM) SE Runtime Environment (11.0.1+13) (build 11.0.1+13-LTS)
Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0.1+13-LTS, mixed mode, tiered, compressed oops, g1 gc, bsd-amd64)
Problematic frame:
C [CoreFoundation+0x8248] CFDictionaryGetValue+0xb
No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
An error report file with more information is saved as:
/Applications/Eclipse.app/Contents/MacOS/hs_err_pid10464.log
If you would like to submit a bug report, please visit:
http://bugreport.java.com/bugreport/crash.jsp
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
Unfortunately, I do not have so much information to share.
Here my setup:
Mojave, v. 10.14.1
Eclipse DSL Tools, v: 2018-09 (4.9.0), Build id: 20180917-1800
java version "11.0.1" 2018-10-16 LTS, Oracle one
What I have tested:
Running the ulimit -c unimited command
Reinstalling Eclipse
Reinstalling my JDK. I also tested on OpenJDK.
Running on a fresh computer. I don't have the bug on macOs Sierra.
I tested the solution mention here:
how to fix “Failed to write core dump. Core dumps have been disabled” error while running java
Thanks for your help.
#Christian Dietrich: many thanks for the link!
Here the current workaround explained in the link: to add the '-nosplash' in Arguments tab of run configuration.
I have installed eclipse on my iMac and when I try to open it, it gives me this error:
Failed to find a Main Class in
"/Applications/Eclipse.app/Contents/MacOS//../Eclipse/ plugins/org.eclipse.equinox.launcher_1.5.0.v20180512-1130.jar".
On my MacBook Pro, everything works fine, but I have done nothing different.
I have checked other posts, but most of them refer to a windows OS. There was an answer which said that it can just open when everything is in an English folder and this is true for me!
Thanking you in advance!
I came across this error after installing Eclipse PDT.
Open your terminal and run the version command: java -version.
If your java version is below 1.8, you will have to update your Java
Runtime Environment to at least 1.8.0 by installing an updated JDK
here.
Then re-run the java version command and your version
should be updated.
You should now be able to install and run
Eclipse.
I have the same issue, but on my MacBookPro. I first installed eclipse Photon, which when starting up prompted me to install Java 6, which I did from https://support.apple.com/kb/DL1572?locale=en_US
Then I also installed the latest JRE (jre-8u171-macosx-x64 as of yesterday). When running eclipse again I started getting this error. Then I tried to run from the command line, and got this error:
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/eclipse/equinox/launcher/Main : Unsupported major.minor version 51.0
When googling that, the answers said that the reason for that is that the Oracle installer does not update the symlink in /usr/bin, which seemed to be confirmed by the fact that running java -version returned this:
java -version
java version "1.6.0_65"
The solutions I found for that were not feasible in MacOS starting in version El Capitan, and I am on High Sierra, so I followed the instructions in this post to fix that, and it worked, now I get:
java -version
java version "1.8.0_171"
Java(TM) SE Runtime Environment (build 1.8.0_171-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.171-b11, mixed mode)
After all of this, however, I get the same "Failed to find a Main Class" error on the dialog as reported initially here, and the same "UnsupportedClassVersionError" on the CLI that I had when the system was still on java 6, so now I am still stuck and out of ideas.
EDIT: FIXED IT!!
I kept thinking that the problem was the java version, it was somehow still using java 6 (which I had installed due to the initial prompt).
So I followed the instructions here to remove what I had installed for the alleged java 6 issue. Then I found this post in the eclipse forums, which stated at the end (comment added by Eric Rizzo on Tue, 14 February 2017 21:56) that this is not an Eclipse message, but rather an OS message, and that one should NOT do that as apple messed things up with that patch. And then it goes to explain that one should install java 8 JDK (NOT just the JRE as I had done). Once I removed Java 6 and installed the full java 8 JDK, it ran fine :)
You can edit the eclipse.ini with your vm configuration in the beginning of the file
-vm
/yourJvmPath/jdk-12.0.1.jdk/bin/java
cat /Applications/Eclipse.app/Contents/Eclipse/eclipse.ini
-vm
/Users/SomeUser/jdk-12.0.1.jdk/bin/java
-startup
../Eclipse/plugins/org.eclipse.equinox.launcher_1.5.400.v20190515-0925.jar
--launcher.library
../Eclipse/plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.1000.v20190125-2016
PD. It works with ApacheDirectoryStudio for MAC
This one works for me with MAC OS Mojave.
You can download the Java SE Development Kit 8u221 for mac from the below link.
jdk-8u221-macosx-x64.dmg
https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
I have installed MongoDB 3.0.4 . When i execute command "mongod" it crashes with message "Mongod.exe has stopped working". Here is problem details
Problem Event Name: APPCRASH
Application Name: mongod.exe
Application Version: 0.0.0.0
Application Timestamp: 557ef9c9
Fault Module Name: MSVCR120.dll
Fault Module Version: 12.0.21005.1
Fault Module Timestamp: 524f83ff
Exception Code: c000001d
Exception Offset: 0000000000092bc3
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: fd3b
Additional Information 2: fd3bb24d4274b34ca613c6f4e63ceb13
Additional Information 3: 3204
Additional Information 4: 3204b56578b4c221b1569b71b387eb68
I am using Windows 7 64 bit operating system. Why this problem ???
Thanks in advance.
I was facing the exact issue with current version 3.0.6 of mongodb. I uninstalled it and installed 2.6.11 verson. And it worked! For your information I am also using Win 7 OS 64 bit.
I had the same problem when launching Worckbench.
I just installed the Visual C++ Redistributable Packages for Visual Studio 2013 and the problem was solved.
Installing Windows 7 SP1 fixed the problem for me.
I have installed MongoDB 3.2.10 using Windows Server 2008 R2 x64, and it was the same problem with you.
The solution is upgrade the OS to SP1.
I have built an installer using the latest Install4J. On the Mac OS, it fails to install with the following message: "An internal error has occuerred (error code: launch path not accessible)".
The same installer for other platforms (Windows 32/64, and Linux) work fine. Has anyone else seen this and know how to fix it?
It turns out, this error was caused by the OpenJDK JRE version i was using. It works fine with the Installed version of the JRE on my Mac.