-
Notifications
You must be signed in to change notification settings - Fork 62
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
GC Seg fault #48
Comments
Do you happen to use the non-devel version of nim that doesn't have this patch yet? nim-lang/Nim#7885 |
Yes - I'm on nim 0.18 - Should I try the devel version? |
Yes please |
I assume that nails it. If not, feel free to reopen. |
Works with the dev build without issues. Thanks! |
Kinda duplicate of #11 |
yglukhov
added a commit
that referenced
this issue
Sep 25, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So I wrote a small module and then when I call it from python, it works fine if it's just a single call.
OTOH, if I call it in a loop - even say just 100 times, then after the 20th time there's a crash [on windows, the debug window opens, on linux I get a message about the GC]
I also tried building with
--gc:none
and in this case, the program completes successfully.Are there guidelines/dos & donts in terms of what data can be returned from nim?
Happy to share code if you want to drop me an email at raghu dot nospam at gmail
The text was updated successfully, but these errors were encountered: