ext: fix memory leak when reentrant/multithreaded v0.3.1

The optional C extension leaked memory due to improper use of
the Ruby API, causing duplicated objects to never be garbage
collected.

I misread the Data_Make_Struct/Data_Wrap_Struct documentation
and ended up passing NULL as the "free" argument instead of -1,
causing the memory to never be freed.

From README.EXT in the MRI source which I misread:
> The free argument is the function to free the pointer
> allocation.  If this is -1, the pointer will be just freed.
> The functions mark and free will be called from garbage
> collector.

0 files changed, 0 insertions, 0 deletions