Skip to content

Should not allow free of already freed scratch ndarray #1

@jalava

Description

@jalava

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions