-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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 when calling kb.get_vector
#9137
Comments
Thanks for the report! I can reproduce this error and it doesn't look platform-specific. We will look into it! |
I can confirm this problem can be reproduced on the following: A trace revealed the problem is related to the following method https://github.com/explosion/spaCy/blob/master/spacy/kb.pyx#L307 I believe specifically to https://github.com/explosion/spaCy/blob/master/spacy/kb.pyx#L315 Which is initialized here https://github.com/explosion/spaCy/blob/master/spacy/kb.pyx#L99 Where |
Hi all, thanks for your patience! An explanation and solution for this bug is provided in #9463. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
How to reproduce the behaviour
When I run this example I get a segmentation fault. I am not sure how to get a stacktrace. I tried to set this env variable
PYTHONFAULTHANDLER=1
but I get only this:I should note that I am using a new MacBook with an M1 chip so it can be something platform specific. Also, it happens only when I serialize KB which was generated with
set_entities
. When I add entity one by one it works just fine.Code to reproduce:
Your Environment
Info about spaCy
The text was updated successfully, but these errors were encountered: