-
Notifications
You must be signed in to change notification settings - Fork 143
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
Segmentation fault (core dumped) on import #46
Comments
"Segmentation fault (core dumped)" usually means that the process crashed due to SIGSEGV. In case of Python, it could be that
In case of This also includes the Can you share what versions of
|
I also suspected it, but import jpype had no apparent problems. My versions are: |
@DeckardSG I have the same versions for both
|
Here it is: 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. |
Same on another machine. Compilation goes well but importing boilerpipe causes python3 to crash |
@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?
The text was updated successfully, but these errors were encountered: