Community
Participate
Working Groups
Created attachment 252657 [details] Crash Log After the installer has finished installing, it offers a button / link to launch. Clicking this crashes the installer. It is likely due to the file being corrupt and unusable.
Unfortunately the native dump doesn't help me a lot to understand what's going on. Generally a VM crash indicates a bug in that VM. In the absence of a Java stack trace I'd need to know what exactly you've done. Did you use the simple mode only? What product did you install and what version of it? What JRE did you pick? Regarding the effect, "crash" means that the installer process terminates with an error exit code? Is there a popup with an error message? Are there any other log files, e.g., in oomph/configuration? Does the product that's supposed to launch actually launch or not?
Eike, 1. Simple mode 2. Installed: Eclipse IDE for Java Developers 3. JRE 1.7.0_71 The pop-up is the standard OS X crash reporting dialog - containing the text attached to the bug. Is the C wrapper common to all 3 platforms?
Thanks for the quick reply ;-) One more question: Into what location on your disk did you install the package? (In reply to comment #2) > Is the C wrapper common to all 3 platforms? On all 3 platforms the C wrapper is the normal Eclipse launcher executable as it is provided by Equinox. On Windows the entire "installer installation" (including the normal Eclipse launcher executable) is self-extracted from an additional native Windows executable, called the "extractor".
Eike, I left the default Users/tim/java directory to test overrides. I put an empty /eclipse directory to see if the case of the directory was considered. Regardless it was the preselected directory of Users/,,/java This is a UX issue on OS X as we need to come up with a better convention. My suggestion will be at worst (in this case): /Applications/Eclipse-Mars If for example it was J2EE /Applications/Eclips-Mars-J2EE Or the like. This way it avoids conflict with existing installations.
Created attachment 252690 [details] MacOS Crash Dialog This is another perspective on the dialog as it was a previous question. This occurred today as a result of: 1. Downloading the installer for MacOS 2. Upgrading the installer via the installer upgrade button 3. Downloading Eclipse IDE for Java Developers via the installer 4. Clicking the launch icon after a successful install
Moving all unresolved bugzillas to 1.2.0...
Moving all unresolved bugzillas to 1.3.0...
Hi Tim, Even though we've had roughly 250,000 downloads of the installer on MacOS since Mars and not heard of a single similar incident we've again looked at the crash log that you've provided. It says that thread 10 is the crashed one. And there libswt-cocoa-4517.jnilib is involved, which makesus think that the problem might be in SWT for MacOS. There is one place in the installer that uses internal SWT code on MacOS. The purpose is to register with the´"system menu" of MacOS. See the following bugzilla: [440389] [MacOS] Clicking application menu "About setup-eclipse" has no effect https://bugs.eclipse.org/bugs/show_bug.cgi?id=440389 We guard all calls to that internal SWT code and ignore any exceptions from there. But there's a rest risk that these calls leave some bad state that causes a crash, for example, at exit time. To make sure that this isn't the case please add the line "-Doomph.cocoa.menu.skip=true" to the installer's eclipse-inst.ini file and try your steps again. Can you still reproduce this crash?
Elke - thank you. This is working for me.
