为什么我的Eclipse Luna 4.4在Debian Wheezy 7.4上与Oracle JDK8 64位崩溃？ [英] Why does my Eclipse Luna 4.4 crash on Debian Wheezy 7.4 with Oracle JDK8 64bit?

问题描述

我已经在Oracle VirtualBox上安装了Debian GNU / Linux 7.4（wheezy）操作系统：

  Java（TM）SE运行时环境（build 1.8.0_11-b12）
 Java HotSpot（TM）64位服务器虚拟机（构建25.11-b03，混合模式） 
  

我下载了Eclipse Luna 4.4。当我试图运行Eclipse时发生错误：

 一个致命错误已被检测到Java运行时环境：
在pc = 0x00007f9e8a42173f，pid = 10942，tid = 140319582553856 
中的SIGSEGV（0xb）JRE版本：Java（TM）SE运行时环境（8.0_11-b12）（build 1.8.0_11- b12）
 Java VM：Java HotSpot（TM）64位服务器虚拟机（25.11-b03混合模式linux-amd64压缩的oops）
问题框架：
 C [libgdk-x11-2.0。 so.0 + 0x5173f] gdk_display_open + 0x3f 
无法写入核心转储。核心转储已被禁用。要启用核心转储，请在启动Java 
之前尝试ulimit -c unlimited
 




所以我在终端上发了一个命令：

  $ ulimit -c unlimited 
 $ ./eclipse 
  

但下一个错误发生：

  Java HotSpot（TM）64位服务器VM警告：忽略选项MaxPermSize = 256m;支持
在8.0 
（java：11276）中被删除：GLib-GObject-WARNING **：无法注册现有类型GdkDisplayManager
（java：11276）：GLib-CRITICAL **： g_once_init_leave：assertion`result！= 0'failed 
（java：11276）：GLib-GObject-CRITICAL **：g_object_new：assertion`G_TYPE_IS_OBJECT（object_type）'failed 
（java：11276） GObject-WARNING **：invalid（NULL）pointer instance 
（java：11276）：GLib-GObject-CRITICAL **：g_signal_connect_data：assertion`G_TYPE_CHECK_INSTANCE（instance）'failed 
（java：11276） GLIB-GObject-WARNING **：invalid（NULL）pointer instance 
（java：11276）：GLib-GObject-CRITICAL **：g_signal_connect_data：assertion`G_TYPE_CHECK_INSTANCE（instance）'failed 
（java：11276 ）：GLib-GObject-WARNING **：无法注册现有类型GdkDisplay
（java：11276）：GLib-CRITICAL **：g_once_init_leave：assertion`result！= 0'failed 
（java： 11276）：GLib-GObject-CRITICAL **：g_type_register_static：assertion`parent_type> 0'failed 
（java：11276）：GLib-CRITICAL **：g_once_init_leave：assertion`result！= 0'failed 
（java：11276）：GLib-GObject-CRITICAL **：g_object_new：assertion `G_TYPE_IS_OBJECT（object_type）'失败
 Java运行环境检测到致命错误：
在pc = 0x00007f216d28473f，pid = 11276，tid = 139782222493440JRE版本：Java（TM）SE的SIGSEGV（0xb）运行环境
  

（8.0_11-b12）（build 1.8.0_11-b12）
Java VM：Java HotSpot（TM）64位服务器虚拟机（25.11-b03混合模式linux-amd64压缩的oops）
问题框架：
C [libgdk-x11-2.0.so.0 + 0x5173f] gdk_display_open + 0x3f
写入核心转储。 default /

  -Dorg.eclipse.swt.browser.DefaultType = mozilla 
  

到eclipse.ini，但没有帮助。

有人可以帮我解决这个问题吗？根据：
https://bugs.eclipse.org/bugs/show_bug.cgi?id=430736

添加到2行eclipse.ini：

   -  launcher.GTK_version 
 2 
  

选项--launcher.GTK_version应该在之前 --launcher.appendVmargs

TIBCOJaspersoft®Studio - Visual Designer for JasperReports的问题（对话框无法正常工作）：

编辑Jaspersoft Studio.ini，这个：

  -startup 
 plugins / org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar 
 --launcher.GTK_version 
 2 
 --launcher.library 
  

或者在启动Jasper Studio之前添加（ runubuntu.sh ）：

 导出SWT_GTK3 = 0 
  

I have Debian GNU/Linux 7.4 (wheezy) OS installed on Oracle VirtualBox and:

java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)

I downloaded Eclipse Luna 4.4. When I was trying to run Eclipse an error occurred:

A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x00007f9e8a42173f, pid=10942, tid=140319582553856
JRE version: Java(TM) SE Runtime Environment (8.0_11-b12) (build 1.8.0_11-b12)
Java VM: Java HotSpot(TM) 64-Bit Server VM (25.11-b03 mixed mode linux-amd64 compressed oops)
Problematic frame:
C  [libgdk-x11-2.0.so.0+0x5173f]  gdk_display_open+0x3f
Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java

So I issued a command in the terminal:

$ ulimit -c unlimited
$ ./eclipse

But the next error occurred:

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support
was removed in 8.0
(java:11276): GLib-GObject-WARNING **: cannot register existing type `GdkDisplayManager'
(java:11276): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed
(java:11276): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(java:11276): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(java:11276): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(java:11276): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(java:11276): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(java:11276): GLib-GObject-WARNING **: cannot register existing type `GdkDisplay'
(java:11276): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed
(java:11276): GLib-GObject-CRITICAL **: g_type_register_static: assertion `parent_type > 0' failed
(java:11276): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed
(java:11276): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x00007f216d28473f, pid=11276, tid=139782222493440JRE version: Java(TM) SE Runtime Environment

(8.0_11-b12) (build 1.8.0_11-b12) Java VM: Java HotSpot(TM) 64-Bit Server VM (25.11-b03 mixed mode linux-amd64 compressed oops) Problematic frame: C [libgdk-x11-2.0.so.0+0x5173f] gdk_display_open+0x3f Core dump written. Default location: /home/abcdef/ECLIPSE_JAVA/eclipse/core or core.11276

I also tried to solve this problem by adding:

-Dorg.eclipse.swt.browser.DefaultType=mozilla

to eclipse.ini, but it didn't help.

Can anybody help me with this problem?

解决方案

According to: https://bugs.eclipse.org/bugs/show_bug.cgi?id=430736

Add to 2 lines eclipse.ini:

--launcher.GTK_version
2

The option --launcher.GTK_version should be before --launcher.appendVmargs

Problem (dialogs does not work properly) with TIBCO Jaspersoft® Studio - Visual Designer for JasperReports:

edit Jaspersoft Studio.ini like this:

-startup
plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar
--launcher.GTK_version
2
--launcher.library

Or add this before start Jasper Studio (runubuntu.sh):

export SWT_GTK3=0

这篇关于为什么我的Eclipse Luna 4.4在Debian Wheezy 7.4上与Oracle JDK8 64位崩溃？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！