Cannot start Studio

MicroEJ Studio
1

Could be partly my fault — a late night, downloaded and ran the installer, which turned out to be the 32-bit, not the 64-bit version. The message I got was this:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000000038250, pid=13813, tid=0x00007f64859af700
#
# JRE version: OpenJDK Runtime Environment (8.0_192-b12) (build 1.8.0_192-20181024121959.buildslave.jdk8u-src-tar--b12)
# Java VM: GraalVM 1.0.0-rc11 (25.192-b12-jvmci-0.53 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  0x0000000000038250
#
# Failed to write core dump. 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:
# /home/daniel/hs_err_pid13813.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp

That’s not the exact message then, just something similar. I then installed the 64-bit version, and got the message above.

As an aside, I did manage to install it on my Windows 10 box, prefer to do my dev work in Linux though.

My setup:

  • Lenovo ThinkPad X201 Tablet, 8GB RAM, 500GB SSD
  • Linux Peppermint, based on Ubuntu 18.04.1
  • GraalVM for Java JRE (based on OpenJDK) — Graal provides a VM that supports for Java, R, some others

My apologies for pasting the log file here, can’t attach it:
<grumble>
can’t even paste it, have to create a reply I guess
</grumble>

[EDIT:] How can I upload a log file, please, the editor won’t accept more than 32000 characters?

2

Could you please confirm which MicroEJ Distribution you are trying to run (MicroEJ Studio/SDK 19.05 ?)

This distribution was tested using JRE builds from https://java.com, and we know it usually works on AdoptOpenJDK 8 LTS builds.

Could you please test with the latest Linux 64bits JRE ( https://javadl.oracle.com/webapps/download/AutoDL?BundleId=240718_5b13a193868b4bf28bcb45c792fce896)

On our side, we will try to reproduce on a Linux environment using a GraalVM build.

Thanks

3

Hi Dan,

Can you try attaching the log again as a .txt file?

Thx,
Gaëtan

4

hs_err_pid13813.log.txt (41.7 KB)

Well, what do you know? That did it, thanks

5 
daniel@x201t ~ $ /opt/MicroEJ/MicroEJ-Studio-19.05/rcp/MicroEJ-Studio 
GraalVM 1.0.0-rc11 warning: ignoring option MaxPermSize=256m; support was removed in 8.0
#
# A fatal error has been detected by the Java Runtime Environment:

Yep, included the command line this time

6

Thanks for the log file. I took a look to the java stack trace at crash and it is failing at early Eclipse Startup phase, when trying to display the splash.

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  org.eclipse.equinox.launcher.JNIBridge._show_splash(Ljava/lang/String;)V+0
j  org.eclipse.equinox.launcher.JNIBridge.showSplash(Ljava/lang/String;)Z+2
j  org.eclipse.equinox.launcher.Main.handleSplash([Ljava/net/URL;)V+158
j  org.eclipse.equinox.launcher.Main.basicRun([Ljava/lang/String;)V+150
j  org.eclipse.equinox.launcher.Main.run([Ljava/lang/String;)I+4
j  org.eclipse.equinox.launcher.Main.main([Ljava/lang/String;)V+10
v  ~StubRoutines::call_stub

After googling the issue, I found a similar topic: https://support.openanalytics.eu/t/phaedra-1-0-6-installation-on-linux-not-working/1418 but no reply / no information available.

Let me know what is the behavior with the java.com distribution.
We can also suspect a wrong SWT/GTK configuration on Linux side. Please have a look to the Linux Specifics section of the MicroEJ Studio/SDK release notes (https://repository.microej.com/p2/).

7

Thanks to all for the effort. In the short term, looks like I’ll have to resort to doing MicroEJ work on my Windows box. Over the longer term, I may just have to revert to Linux Mint, which gave me fewer problems with development software in general — e.g., Eclipse, Netbeans, etc

8

OK, I’m here again, with a bit of good news. I’m still on Peppermint, and finally got MicroEJ Studio to run, albeit 4.0.0 — indicates something about 4.1.5, hope the developers have time to look into it.
Next up: downloading a virtual device. My target devices are mainly ESP boards: an 8266, a couple of 32s — maybe more of the latter, although I still expect to use to 8266 — and a TTGO-Journal. I did download a .vde earlier, which 4.0.0 doesn’t seem to like. I do have a .jpf, although not sure it’s for the ESPs, will look into that later

9

Hi @Dan.Escasa,

.vde are the extention file for MicroEJ Virtual Device: A MicroEJ Virtual Device is a software package that includes the similar of a MicroEJ-ready device (Runtime, Libraries and Resident Applications) for testing a MicroEJ Sandboxed Application in MicroEJ Studio. Virtual devices can be downloaded here.
Those extentions are only supported on MicroEJ 5 (http://developer.microej.com/5/getting-started-studio.php?web=true).
.jpf are binary platform files (or old virtual device), MicroEJ Platform: A MicroEJ Platform is a software package includes the build of a C board support package (BSP, with or without RTOS), a MicroEJ Architecture, adaptation layers, the MicroEJ Simulator and its associated MicroEJ Mocks.

Regards,