-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DynComp: a fatal error has been detected by the Java Runtime Environment (ClassNotFoundException) #341
Comments
I am unable to reproduce this problem. I followed your steps and all looks ok: |
Thank you for your reply. Here is my machine info:
I can always reproduce it on this machine. I'll try if the problem could be reproduced on other machines and update it here. |
I was able to reproduce on Ubuntu 18.04. I haven't tried 20.04. Are you able to try 20.04? |
Yes, my 20.04 is a windows subsystem, it is a little bit slow. It is compiling DynComp now, I will update it later. |
I can reproduce it on Ubuntu 20.04.
|
I have found the problem and it appears to be a bug in the Ubuntu JVM. The root cause is that the build of Chart19f fails to build a valid version of lib/itext-2.0.6.jar: markro ~/defects4j/Chart19f]$ jar -tf lib/itext-2.0.6.jar If you remove this jar from CLASSPATH all works fine. If you leave the bad jar in the classpath both CentOS and Fedora still work fine and output the message: Ubuntu core dumps instead => I think its a bug in Ubuntu JVM. Bottom line: remove itext-2.0.6.jar from classpath and/or run on Fedora instead. |
Hi,
I met another JVM fatal error, different from #340. It only happens to Chart-19. Below is the output
If I run the tests directly, it works fine,
The steps to reproduce the issue:
CLASSPATH=$(find "$PWD" -name '*.jar' -type f -printf ':%p\n' | sort -u | tr -d '\n'); java -Xmx43G -cp $DAIKONDIR/daikon.jar:build/:build-tests/$CLASSPATH:<TestRunner path> TestRunner org.jfree.chart.plot.junit.CategoryPlotTests::testGetRangeAxisIndex org.jfree.chart.plot.junit.CategoryPlotTests::testGetDomainAxisIndex
The text was updated successfully, but these errors were encountered: