-
Notifications
You must be signed in to change notification settings - Fork 12
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
Panic on cgo call of secp256k1 #203
Comments
Hey, @nepet this never happened to us so far. Any chance you can provide us with a "minimal repro" go file that triggers this panic? From the stack trace it seems to originate from |
Thanks for checking on this @tiero! go-elements/confidential/confidential.go Lines 185 to 188 in 17f0c89
The stack trace seems to originate from the |
oh, ok seems then related to some memory leak. I just quickly read on your reference issue, please be sure to defer any calls, so cgo will release memory before panic |
https://musl.libc.org/
|
happened again ... same place ... |
I think the best way would be to have a single go file, with the code stripped down to what caused these crashes, and will then start investigating from there if it's something related to our implementation and/or usage of cgo calls or if it's a golang cgo specific thing. Eventually then using a Dockerfile we can test on Alpine too. Thanks |
@nepet since we're reproducing this crash easily on our alpine deployment, could you make a test commit that prints out all the inputs before it calls this so we could try to make a minimal reproducer out of it? |
Also paging @altafan in case you have ever experienced this or tried already on alpine/musl. We never tested outside debian-like evn to be honest |
Hi folks,
Does anyone of you here have an idea why we are getting this panic log?
Cheers,
Peter
The text was updated successfully, but these errors were encountered: