Open DeckardSG opened 7 years ago
"Segmentation fault (core dumped)" usually means that the process crashed due to SIGSEGV. In case of Python, it could be that
In case of import boilerpipe
, the error could happen due to the code called from init.py
This also includes the jpype
module. I suspect that it is the jpype
module that is causing the failure.
Can you share what versions of jpype
and Java you are running ?
In [1]: import jpype
In [2]: jpype.__version__
Out[2]: '0.6.2'
I also suspected it, but import jpype had no apparent problems. My versions are: jpype = 0.6.2 java version "1.8.0_131" Java(TM) SE Runtime Environment (build 1.8.0_131-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
@DeckardSG I have the same versions for both jpype
and Java. To gain more insight, can you share the output of following command in a pastebin:
$ python -v -c 'import boilerpipe; print "DONE"'
Here it is: https://pastebin.com/Tzex6EiE
I have started a new project from scratch in another machine and it seems to work, however the old ones are still showing the segfault.
Thanks for your time and sorry for the trouble.
Same here. I have the same version of jpype and python crashes on first import line. Python 3.6 Java 1.8.0_152-b16
Same on another machine. Compilation goes well but importing boilerpipe causes python3 to crash Any idea how to progress with that?
@rubimazaki It is unlikely for me to find the root cause of this Seg Fault, because I only have Fedora 25 machine -- and it works for me. Could you try it once more and share your OS details, the commands used and logs ?
I am obtaining a "Segmentation fault (core dumped)" whenever I tried to import boilerpipe. It just happened in all my installations suddenly, as they were working fine just a few hours ago. The segmentation fault occurs just by typing "import boilerpipe" on Ubuntu 16.04.2 LTS machines. It seems to work fine on MacOS 10.11. I tried to double the heap memory on JVM but it did not work. Any suggestions?