承保范围致命错误(EclEmma) [英] Coverage fatal error (EclEmma)

查看:263
本文介绍了承保范围致命错误(EclEmma)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使用Eclipse Mars 4.5.2.在为我的应用程序运行覆盖测试时,到目前为止,它有317种测试方法,当它即将完成时(运行大约274种方法),我遇到了找不到解决方案的错误.

I am using Eclipse Mars 4.5.2. When running coverage tests for my application, which has 317 test methods so far, when it's about to finish (around 274 methods run), I am getting errors I can't find a solution to.

首先是一个弹出窗口,上面写着:

First a popup window saying:

无覆盖数据

在此期间未收集覆盖率数据覆盖会话.

No coverage data has been collected during this coverage session.

请不要手动终止Java进程来自Eclipse.

Please do not terminate the Java process manually from Eclipse.

secon弹出窗口:

A secon popup window:

'com.mountainminds.eclemma.internal.core.launching.AgentServer'具有遇到了问题.转储承保日期(代码5013)时出错.

'com.mountainminds.eclemma.internal.core.launching.AgentServer' has encountered a problem. Error while dumping coverage date (code 5013).

[详细信息:]转储coverage数据时出错(代码5013).联系重置

[Details:] Error while dumping coverage data (code 5013). Connection reset

然后显示以下控制台日志:

And then the following console log:

Java运行时环境检测到致命错误:

A fatal error has been detected by the Java Runtime Environment:

EXCEPTION_ACCESS_VIOLATION(0xc0000005)at pc = 0x000000005f9b96af,pid = 2024,tid = 3772

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000005f9b96af, pid=2024, tid=3772

JRE版本:Java(TM)SE运行时环境(8.0_66-b18)(内部版本1.8.0_66-b18)Java虚拟机:Java HotSpot(TM)64位服务器虚拟机(25.66-b18混合模式Windows-amd64压缩的oops)有问题的框架:V [jvm.dll + 0x4b96af]

JRE version: Java(TM) SE Runtime Environment (8.0_66-b18) (build 1.8.0_66-b18) Java VM: Java HotSpot(TM) 64-Bit Server VM (25.66-b18 mixed mode windows-amd64 compressed oops) Problematic frame: V [jvm.dll+0x4b96af]

无法写入核心转储.默认情况下,在客户端版本的Windows上不启用小型转储

Failed to write core dump. Minidumps are not enabled by default on client versions of Windows

包含更多信息的错误报告文件另存为:X:\ xxxxx \ hs_err_pid2024.log

An error report file with more information is saved as: X:\xxxxx\hs_err_pid2024.log

编译器重播数据另存为:X:\ xxxxx \ replay_pid2024.log

Compiler replay data is saved as: X:\xxxxx\replay_pid2024.log

如果您要提交错误报告,请访问: http://bugreport.java.com/bugreport/crash.jsp

If you would like to submit a bug report, please visit: http://bugreport.java.com/bugreport/crash.jsp

这个问题困扰了我两周了,正如我所说,我找不到任何解决方案,只是四到五年前EclEmma网站上的类似错误报告.

I have been suffering this issue for a couple of weeks and, as I said, I can't find any solution, just similar bug reports in the EclEmma site from four or five years ago.

我尝试为JUnit设置以下JVM参数: -Xms2g -Xmx2g .

I have tried setting the following JVM arguments for JUnit: -Xms2g -Xmx2g.

我的测试没有任何数据库连接,服务器连接或网络连接.他们也不发出任何HTTP请求.

My tests don't have any database connection, server connection nor network connection. They don't make any HTTP request either.

我尝试重新安装EclEmma插件以及重新安装Eclipse.问题仍然存在.

I have tried reinstalling the EclEmma plugin as well as reinstalling Eclipse. The issue persisted.

推荐答案

更新coverage配置.转到参数"部分,然后在"VM参数"部分的"perm size"参数下面添加:-XX:MaxPermSize = 1225m

Update the coverage configuration. Go to the Arguments section and add below perm size argument in VM arguments section: -XX:MaxPermSize=1225m

这篇关于承保范围致命错误(EclEmma)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆