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.

Sign up for GitHub

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

Jump to bottom

Should not allow free of already freed scratch ndarray #1

Open

jalava opened this issue Jun 8, 2015 · 1 comment

jalava commented Jun 8, 2015

Had very strange results after calling free twice on same ndarray. After that pool.zeroes started returning buffers that were currently in use.

To prevent this, I think you should keep flag with ndarray of it's malloc state and throw error if you are trying to free already released buffer.

Member

mikolalysenko commented Jun 8, 2015

Maybe we could make a debug version of ndarray-scratch which tests to see if an array was double free'd.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment