search

osate / osate2

Open Source AADL2 Tool Environment
http://osate.org
Eclipse Public License 2.0
35 stars 8 forks source link

OSATE 2.6.0 plugin crashes non-"Modeling Tools" Eclipse package. #2061

Closed schwerdf closed 4 years ago

schwerdf commented 4 years ago

Summary

In at least one Eclipse package variant other than "Modeling Tools," when OSATE 2.6.0 is installed as a plugin, Eclipse subsequently fails to launch, rendering it unusable.

Steps to Reproduce

  1. Start with a clean copy of Eclipse 2019-09, "RCP and RAP Developers" package variant.
  2. Add update sites for OSATE and ELK (exported update site list attached).
  3. Install all components under the "OSATE2 for AADL2" category.
  4. Restart Eclipse after installation.
  5. Exit Eclipse, then try to relaunch.
  6. Note that Eclipse fails to launch, with an error dialog pointing the user to the workspace log (log attached).

    Environment

lwrage commented 4 years ago

I cannot reproduce this. Maybe https://stackoverflow.com/questions/55245607/cannot-launch-eclipse-because-the-instance-data-location-has-not-been-specified helps.

schwerdf commented 4 years ago

I tried removing the dataAreaRequiresExplicitInit line. This makes it possible to launch Eclipse, but also makes it impossible to select a workspace on launch. On further examination, the cause of the crash seems to be EMV2: the crash only happens when EMV2 and/or its source code is installed.

lwrage commented 4 years ago

Did you install a downloaded package or did you use the eclipse installer?

schwerdf commented 4 years ago

A downloaded package.

lwrage commented 4 years ago

Could you try with the eclipse installer? Maybe there's a difference. I can't reproduce it either way.

schwerdf commented 4 years ago

Same result when using the installer -- after EMV2 is added, Eclipse crashes on startup.

schwerdf commented 4 years ago

Are you installing the OSATE plugin via some other method than the "Install New Software" dialog?

lwrage commented 4 years ago

No, that's what I was doing. Unfortunately I have no idea what could cause this problem. However, on my machine I have recorded user preferences that are automatically applied to each Eclipse workspace. Maybe that makes a difference. Maybe just setting some preference from the UI is needed.

schwerdf commented 4 years ago

I stood up a clean Linux VM (Fedora 31, live distribution) and installed Eclipse (through the installer) and OSATE on there. It still crashed on exit and relaunch. Whatever is preventing your reproducing this, it must be specific to your machine.

lwrage commented 4 years ago

Again, it works for me in a fresh Ubuntu 18.04 virtual machine with OpenJDK 8.

philip-alldredge commented 4 years ago

This is just a wild guess but could SELinux be blocking something in OSATE or Java? I believe Fedora defaults to it being on.

See below for checking the SELinux logs and how to temporarily disable it. https://fedoraproject.org/wiki/SELinux_FAQ#How_do_I_find_out_whether_SELinux_is_denying_access_for_any_software.3F https://fedoraproject.org/wiki/SELinux_FAQ#How_do_I_enable_or_disable_SELinux_.3F

schwerdf commented 4 years ago

This is very strange: I stood up an Ubuntu 18.04 VM, installed OpenJDK 8 via the universe repository, Eclipse RCP/RAP via the installer -- still got the crash on exit and relaunch after installing the OSATE plugin. I am now completely out of ideas as to what the point of divergence could be.

lwrage commented 4 years ago

I forgot the second restart step with the Ubuntu VM. I am now able to reproduce the issue with "Eclipse for RCP and RAP Developers." I also tried with "Eclipse for Java Developers" which works just fine. I have no idea how this could be fixed, and I don't think it's worth the effort. I will add this as a known issue to the release notes.