简体   繁体   English

Tomcat使用“无法编写核心转储”崩溃Eclipse Kepler。

[英]Tomcat crashes Eclipse Kepler with “Failed to write core dump.”

After upgrading my Ubuntu from 12.04 to 14.04 I've faced some problems on deploying my application with Tomcat in Eclipse. 将我的Ubuntu从12.04升级到14.04后,我在使用Eclipse中的Tomcat部署应用程序时遇到了一些问题。 When I run my application, Tomcat starts successfully, and then, before the internal Eclipse web-browser opening, it crashes, giving me the next log file: 当我运行我的应用程序时,Tomcat成功启动,然后,在内部Eclipse Web浏览器打开之前,它崩溃,给我下一个日志文件:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f50a9c90ca9, pid=19115, tid=139985944897280
#
# JRE version: Java(TM) SE Runtime Environment (7.0_55-b13) (build 1.7.0_55-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.55-b03 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libwebkitgtk-1.0.so.0+0x461ca9]  webkit_web_view_get_type+0x2489
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

---------------  T H R E A D  ---------------

Current thread (0x00007f50fc00a000):  JavaThread "main" [_thread_in_native, id=19118, stack(0x00007f510474e000,0x00007f510484f000)]

siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x0000000000000000

Registers:
....
....
....
---------------  S Y S T E M  ---------------

OS:jessie/sid

uname:Linux 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64
libc:glibc 2.19 NPTL 2.19 
rlimit: STACK 8192k, CORE 0k, NPROC 15837, NOFILE 4096, AS infinity
load average:1,41 1,37 1,59

/proc/meminfo:
MemTotal:        2048668 kB
MemFree:           72176 kB
Buffers:            3084 kB
Cached:           302944 kB
SwapCached:         1704 kB
Active:          1308052 kB
Inactive:         498300 kB
Active(anon):    1213508 kB
Inactive(anon):   404816 kB
Active(file):      94544 kB
Inactive(file):    93484 kB
Unevictable:          32 kB
Mlocked:              32 kB
SwapTotal:       1999868 kB
SwapFree:        1877512 kB
Dirty:               412 kB
Writeback:             0 kB
AnonPages:       1498712 kB
Mapped:           202676 kB
Shmem:            118016 kB
Slab:              65584 kB
SReclaimable:      36836 kB
SUnreclaim:        28748 kB
KernelStack:        4056 kB
PageTables:        35320 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:     3024200 kB
Committed_AS:    4928148 kB
VmallocTotal:   34359738367 kB
VmallocUsed:      325620 kB
VmallocChunk:   34359354596 kB
HardwareCorrupted:     0 kB
AnonHugePages:    124928 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
DirectMap4k:       56192 kB
DirectMap2M:     2039808 kB


CPU:total 2 (2 cores per cpu, 1 threads per core) family 6 model 15 stepping 13, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, tsc

/proc/cpuinfo:
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model       : 15
model name  : Intel(R) Core(TM)2 Duo CPU     E4600  @ 2.40GHz
stepping    : 13
microcode   : 0xa1
cpu MHz     : 2400.000
cache size  : 2048 KB
physical id : 0
siblings    : 2
core id     : 0
cpu cores   : 2
apicid      : 0
initial apicid  : 0
fpu     : yes
fpu_exception   : yes
cpuid level : 10
wp      : yes
flags       : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm
bogomips    : 4799.49
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model       : 15
model name  : Intel(R) Core(TM)2 Duo CPU     E4600  @ 2.40GHz
stepping    : 13
microcode   : 0xa1
cpu MHz     : 2400.000
cache size  : 2048 KB
physical id : 0
siblings    : 2
core id     : 1
cpu cores   : 2
apicid      : 1
initial apicid  : 1
fpu     : yes
fpu_exception   : yes
cpuid level : 10
wp      : yes
flags       : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm
bogomips    : 4799.49
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:



Memory: 4k page, physical 2048668k(72052k free), swap 1999868k(1877512k free)

vm_info: Java HotSpot(TM) 64-Bit Server VM (24.55-b03) for linux-amd64 JRE (1.7.0_55-b13), built on Mar 17 2014 19:43:58 by "java_re" with gcc 4.3.0 20080428 (Red Hat 4.3.0-8)

time: Sat May 10 20:05:03 2014
elapsed time: 351 seconds

I've read the recommended issues on this staff, but nothing helped. 我已经阅读了这个工作人员的推荐问题,但没有任何帮助。 (There are no so much of them.) Also, I've noticed that with using not the internal Eclipse web-browser, but the external one (Firefox, etc.) there are no such a problem. (它们没有那么多。)另外,我注意到,不使用内部Eclipse Web浏览器,而是使用外部浏览器(Firefox等),没有这样的问题。 So, the thing that crashes my application is somehow connected with this internal web-browser. 因此,崩溃我的应用程序的东西与这个内部Web浏览器有某种联系。 If somebody also had such a problem and found the issue, please help. 如果有人也有这样的问题并发现了问题,请帮忙。

This just worked for me: 这对我有用:

sudo apt-get remove libwebkitgtk-1.0-0
sudo apt-get insert libwebkitgtk-3.0-0

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 Eclipse(C ++)崩溃无法编写核心转储。 核心转储已被禁用 - Eclipse (C++) crash Failed to write core dump. Core dumps have been disabled 无法编写核心转储。 默认情况下,Eclipse中的客户端版本的Windows未启用Minidump - Failed to write core dump. Minidumps are not enabled by default on client versions of Windows in Eclipse 无法写入核心转储。 核心转储已被禁用 - Failed to write core dump. Core dumps have been disabled 如何修复“无法编写核心转储。 运行java时,核心转储已被禁用“错误 - how to fix “Failed to write core dump. Core dumps have been disabled” error while running java 无法写入核心转储。 默认情况下,在Windows客户端版本上不启用小型转储,而从Java调用dll - Failed to write core dump. Minidumps are not enabled by default on client versions of Windows, while callin dll from java 无法编写核心转储。默认情况下,在客户端版本的Windows上未启用小型转储 - Failed to write core dump. Minidumps are not enabled by default on client versions of Windows 无法写入核心转储。 默认情况下,客户端版本的 Windows 不启用小型转储 - Failed to write core dump. minidumps are not enabled by default on client version of windows 如何解决致命错误“ EXCEPTION_ACCES_VIOLATION”和“写入核心转储失败”。 - How to resolve the fatal error “EXCEPTION_ACCES_VIOLATION” with “Failed to write core dump.” 无法写入核心转储。 默认情况下,在Windows 7 32位客户端版本上不启用小型转储 - Failed to write core dump. Minidumps are not enabled by default on client versions of Windows 7 32-bit 无法写入核心转储。 默认情况下,在IntelliJ中Windows的客户端版本上未启用小型转储 - Failed to write core dump. Minidumps are not enabled by default on client versions of Windows in IntelliJ
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM