Open peidong-hu opened 6 years ago
Been a while here... I am getting what appears to be the same crash, mine occurs during the test portion of mvn package
. with almost the same module and frame:
C [libc.so.6+0x804dc] cfree+0x1c
I have set up for this build on a centos7/oracle JDK8 docker image. GCC version gcc-c++.x86_64 0:4.8.5-16.el7_4.2
The compile completed successfully apart from a few C/C++warnings :
warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
Did you ever resolve this issue?
relevant build output:
Training cbow word-embedding ...
Read 0M words
Number of words: 19
Number of labels: 0
Progress: 100.0% words/sec/thread: 26 lr: 0.000000 loss: 0.000000 eta: 0h0m
Text: 'I like soccer', label: '__label__soccer'
Text: 'What is the most popular sport in the US ?', label: '__label__football', probability: 0.500000
Text: 'Do you like soccer ?'
label: '__label__soccer', probability: 0.500000
label: '__label__football', probability: 0.498047
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fc0d15e74dc, pid=433, tid=140465749038848
#
# JRE version: Java(TM) SE Runtime Environment (8.0_73-b02) (build 1.8.0_73-b02)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.73-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libc.so.6+0x804dc] cfree+0x1c
#
Actually I think I have resolved this following the recommendation over at #29
The master at fastText has moved way past what it was on Nov 7, and the head of master did NOT work for me, however picking up commit c5cb6b2d0e295e58cfa827e38d2e9b1e0cbe09e4 (fasttext commit on Nov7) has gotten the tests to run and mvn package
to complete successfully!
Now if we could get a maintainer to check out issue #29 and maybe pull in the fix!
Nope, I used a workaround to wrap it as web service and deployed with docker as back end microservice. And then instead of close the jfastText, I just restart docker container to avoid the jfastText's crash impacts all my application.
Peidong
On Wed, Jul 11, 2018, 16:24 thunderstumpges notifications@github.com wrote:
Been a while here... I am getting what appears to be the same crash, mine occurs during the test portion of mvn package. with almost the same module and frame: C [libc.so.6+0x804dc] cfree+0x1c
I have set up for this build on a centos7/oracle JDK8 docker image. GCC version gcc-c++.x86_64 0:4.8.5-16.el7_4.2
The compile completed successfully apart from a few C/C++warnings : warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
Did you ever resolve this issue?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/vinhkhuc/JFastText/issues/27#issuecomment-404314610, or mute the thread https://github.com/notifications/unsubscribe-auth/AHSwi8i104rvw6bn63wa61iL-2Cb60x8ks5uFm0WgaJpZM4QjF-P .
Hi when my java code calls .close() before destroy the bean in spring container, I got the jvm crashed with the error as blow,
A fatal error has been detected by the Java Runtime Environment:
#
SIGSEGV (0xb) at pc=0x00007fe80add9d1c, pid=4700, tid=0x00007fe75f8ec700
#
JRE version: Java(TM) SE Runtime Environment (8.0_144-b01) (build 1.8.0_144-b01)
Java VM: Java HotSpot(TM) 64-Bit Server VM (25.144-b01 mixed mode linux-amd64 compressed oops)
Problematic frame:
C [libc.so.6+0x82d1c] cfree+0x1c
#
Core dump written. Default location: /home/peidong/Downloads/cuba/sts-bundle/sts-3.9.0.RELEASE/core or core.4700
#
An error report file with more information is saved as:
/home/peidong/Downloads/cuba/sts-bundle/sts-3.9.0.RELEASE/hs_err_pid4700.log
#
If you would like to submit a bug report, please visit:
http://bugreport.java.com/bugreport/crash.jsp
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
#