You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to track down a strange panic when this library is combined with some others. It's entirely possible that it has nothing to do with DataDog/zstd, but i can't reduce my test case any further.
You are using the Compress method in your example which is really simple and 20 lines of code (source) so I don't think there is something from the bindings side.
Looking at the C code, there is an object allocation "outside" the go code for the context (source), but this is created and freed during the C call so it shouldn't make the go runtime panic.
Hi, thanks so much for releasing this binding.
I'm trying to track down a strange panic when this library is combined with some others. It's entirely possible that it has nothing to do with
DataDog/zstd
, but i can't reduce my test case any further.Would you be able to comment on golang/go#19468 (comment) ?
Is there any chance the C code in this library is writing to memory it doesn't own?
The text was updated successfully, but these errors were encountered: