skip to Main Content

I have two classes, "PeerMessage" and "PeerMessageOps" (this is just an example). PeerMessageOps contains constant values that PeerMessage class accesses to. But I don’t know why, every time I do the "PeerMessageOps.thing" from PeerMessage class, Eclipse stops running and exits leaving an hr_err_pid.log archive in personal folder (I don’t understand anything in there). This started happening after I incorporated new source archives to an already existing project. This also happen with any of the previous archives that I was already using. If i don’t access to one class from another this problem doesn’t happen and everything runs normally.

hr_err_pid.log (screenshot):

A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007884fd3b61f8, pid=3363, tid=3364
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.9+9 (17.0.9+9) (build 17.0.9+9)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.9+9 (17.0.9+9, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C  [libwebkit2gtk-4.0.so.37+0xdb61f8]
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E" (or dumping to /home/mpatari/core.3363)
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

---------------  S U M M A R Y ------------

Command Line: -Dosgi.requiredJavaVersion=17 [email protected]/eclipse-workspace -Dosgi.dataAreaRequiresExplicitInit=true -Dorg.eclipse.swt.graphics.Resource.reportNonDisposed=true -Xms256m -Xmx2048m -XX:+UseG1GC -XX:+UseStringDeduplication --add-modules=ALL-SYSTEM -Declipse.p2.max.threads=10 -Doomph.update.url=https://download.eclipse.org/oomph/updates/milestone/latest -Doomph.redirection.index.redirection=index:/->https://raw.githubusercontent.com/eclipse-oomph/oomph/master/setups/ --add-opens=java.base/java.lang=ALL-UNNAMED -Dorg.eclipse.swt.browser.DefaultType=mozilla /home/mpatari/eclipse/jee-2023-092/eclipse//plugins/org.eclipse.equinox.launcher_1.6.500.v20230717-2134.jar -os linux -ws gtk -arch x86_64 -showsplash /home/mpatari/.p2/pool/plugins/org.eclipse.epp.package.common_4.29.0.20230907-1200/splash.bmp -launcher /home/mpatari/eclipse/jee-2023-092/eclipse/eclipse -name Eclipse --launcher.library /home/mpatari/.p2/pool/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.2.700.v20221108-1024/eclipse_11801.so -startup /home/mpatari/eclipse/jee-2023-092/eclipse//plugins/org.eclipse.equinox.launcher_1.6.500.v20230717-2134.jar --launcher.appendVmargs -exitdata 2 -product org.eclipse.epp.package.jee.product -vm /home/mpatari/.p2/pool/plugins/org.eclipse.justj.openjdk.hotspot.jre.full.linux.x86_64_17.0.9.v20231028-0858/jre/bin/java -vmargs -Dosgi.requiredJavaVersion=17 [email protected]/eclipse-workspace -Dosgi.dataAreaRequiresExplicitInit=true -Dorg.eclipse.swt.graphics.Resource.reportNonDisposed=true -Dsun.java.command=Eclipse -Xms256m -Xmx2048m -XX:+UseG1GC -XX:+UseStringDeduplication --add-modules=ALL-SYSTEM -Declipse.p2.max.threads=10 -Doomph.update.url=https://download.eclipse.org/oomph/updates/milestone/latest -Doomph.redirection.index.redirection=index:/->https://raw.githubusercontent.com/eclipse-oomph/oomph/master/setups/ --add-opens=java.base/java.lang=ALL-UNNAMED -Dorg.eclipse.swt.browser.DefaultType=mozilla -jar /home/mpatari/eclipse/jee-2023-092/eclipse//plugins/org.eclipse.equinox.launcher_1.6.500.v20230717-2134.jar

Host: 12th Gen Intel(R) Core(TM) i3-12100, 8 cores, 7G, Ubuntu 22.04.2 LTS
Time: Thu Apr 18 12:46:35 2024 IST elapsed time: 678.075570 seconds (0d 0h 11m 18s)

I’ve tried reinstalling Eclipse and create a new workspace to import previous project and problem is still there. I’m running Eclipse from Ubuntu and project is in Java. I also checked Eclipse is updated to the last version. Would be very thankful for a response.

2

Answers


  1. This is a known issue that has already been fixed for the upcoming Eclipse IDE version 2024-06 (4.32) which will be released on June 12, 2024.

    See Eclipse SWT issue #381 – Eclipse crashes with # C [libwebkit2gtk-4.0.so.37+0xbc8316]

    As workaround you can use the first (or as soon as available, another) milestone of the upcoming release until the Eclipse IDE 2024-06 (4.32) will be released.

    Login or Signup to reply.
  2. This is a workaround:

    cd eclipse
    export GDK_BACKEND=x11;
    ./eclipse 
    

    Wayland is a buggy X11 replacement. Using GDK_BACKEND=x11 forces a compatibility-mode. After an update of ubuntu you could try to remove that GDK_BACKEND to check if eclipse works normal again.

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search