Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Overture 2.6.0 displays error-occurred dialog #663

Closed
Pytheas01 opened this issue Jan 28, 2018 · 13 comments
Closed

Overture 2.6.0 displays error-occurred dialog #663

Pytheas01 opened this issue Jan 28, 2018 · 13 comments
Milestone
v2.6.0

Comments

@Pytheas01
Copy link

Pytheas01 commented Jan 28, 2018 •
edited
Loading

Description

When you double-click Overture 2.6.0, a dialog appears stating that an error occurred and that you should refer to the log in the /Users///.metadata/.log directory.

Steps to Reproduce

  1. Install Overture 64-bit Mac say, in /Applications/Overture Directory

  2. Specify the workspace's path; e.g. /Users//Documents/Overture/workspace2

  3. Double-click the application

Expected behavior:

Overture runs

Actual behavior:

A dialog appears stating that an error occurred and that you should refer to the log in the /Users///.metadata/.log directory.
Yet, the .metadata directory is empty.

Reproduces how often: [What percentage of the time does it reproduce?]

Versions

2.6.0 64-bit Mac on MacOSX 10.12.6 (Sierra)

java version "9.0.1"
Java(TM) SE Runtime Environment (build 9.0.1+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode)

Additional Information
@peterwvj peterwvj added this to the v2.6.0 milestone Jan 29, 2018
@peterwvj
Copy link
Member

Thanks for reporting.

Could you try to follow the instructions listed in the FAQ and let me know if that works.

I see you're testing the release candidate - thanks (2.6.0 isn't out yet)! This issue might be caused by the release candidate not being signed. I forgot to mention that in the email when I sent out the release candidate. Can you confirm that Overture 2.5.4, downloaded from http://overturetool.org/download/ , works on your machine?

Once Overture 2.6.0 is released, it will be signed.

@peterwvj
Copy link
Member

If the suggestion above doesn't fix your issue then try the suggestion below.

I see you're using Java 9.

Overture builds against Eclipse (Oxygen). Unfortunately, there's a bug in Eclipse that causes it to crash on all Java 9 builds. You'll find the corresponding bug report here. Assuming that your issue is Java 9 related: does any of the workarounds suggested there work?

@Pytheas01
Copy link
Author

Pytheas01 commented Jan 29, 2018 via email

@peterwvj
Copy link
Member

peterwvj commented Jan 30, 2018 •
edited
Loading

I still think that the problem is related to the Java9 bug in Eclipse. Recently, there was a MAC (Sierra) user who had a similar problem. He was also using Java9. He fixed the issue by changing his Overture.ini within Overture.app to:

-startup
../Eclipse/plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
--launcher.library
../Eclipse/plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.550.v20170928-1359
-vmargs
--add-modules=java.se.ee
-Dosgi.requiredJavaVersion=1.8
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
-Xms256m
-Xmx1024m

I'm not sure you need everythng listed there. To begin with you could try to add the vmargs. Also the org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar and org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.550.v20170928-1359 files may have slightly different names on your machine, I'm not sure.

Does that work?

@DragosDumitrache
Copy link

@peterwvj I've tried your suggestion above but didn't work. What did work was adding the following VM flag to the Overture.ini file.

-vm
/Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents/Home/bin/java

Your actual jdk version may differ, but that seems to fix it

@peterwvj
Copy link
Member

peterwvj commented Feb 2, 2018

That's excellent - thanks for letting us know about your fix This confirms that the issue was related to the Java 9 bug in Eclipse. I'll consider this issue closed for now.

@peterwvj peterwvj closed this as completed Feb 2, 2018
@Pytheas01
Copy link
Author

Pytheas01 commented Feb 2, 2018 via email

@peterwvj
Copy link
Member

peterwvj commented Feb 2, 2018

Sorry for closing the issue, I simply forgot that @PHIROC 's issue had not been solved yet. I'll re-open the issue for now. Let us know when you have tested it on your machine - thanks.

@peterwvj peterwvj reopened this Feb 2, 2018
@Pytheas01
Copy link
Author

Pytheas01 commented Feb 2, 2018 via email

@DragosDumitrache
Copy link

@PHIROC Apologies, I should have mentioned, specify the -vm before the vmargs. That should fix it. Are you also using the jdk 1.8.0_144? You should be able to navigate to it easily then. Otherwise, update with the right version as necessary.

@Pytheas01
Copy link
Author

Pytheas01 commented Feb 2, 2018 via email

@peterwvj
Copy link
Member

peterwvj commented Feb 3, 2018

Very good, guys. I'll close the issue.

@peterwvj peterwvj closed this as completed Feb 3, 2018
@peterwvj
Copy link
Member

Another option worth trying, if you want to run Overture (or just regular Eclipse) on a Java 9 VM is to add the following line to your Overture.ini file:

--add-modules=ALL-SYSTEM

Source: https://wiki.eclipse.org/Configure_Eclipse_for_Java_9#Configure_Eclipse_for_Java_9_modules

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v2.6.0
Development

No branches or pull requests
3 participants
@peterwvj @DragosDumitrache @Pytheas01