Skip Menu |

This queue is for tickets about the Text-Levenshtein-Damerau-XS CPAN distribution.

Report information
The Basics
Id: 82876
Status: resolved
Priority: 0/
Queue: Text-Levenshtein-Damerau-XS

People
Owner: Nobody in particular
Requestors: DROLSKY [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 2.6
Fixed in: 2.7



Subject: 2.6 leaks memory
The change from alloca to malloc appears to have introduced a memory leak, since there's no corresponding free call. I changed this back and the memory leak in my app went away. I suppose you could also add an explicit free. Either way, why use alloca for some allocations and malloc for others?
On Mon Jan 21 18:51:42 2013, DROLSKY wrote: Show quoted text
> The change from alloca to malloc appears to have introduced a memory > leak, since there's no corresponding free call. I changed this back
and Show quoted text
> the memory leak in my app went away. I suppose you could also add an > explicit free. > > Either way, why use alloca for some allocations and malloc for others?
Will be fixed in 2.7, just waiting for some server maintenance. I had already caught this, but apparently forgot to push it. Using alloca was originally an attempted fix at MSVC complaining about variable length array. I added some other attempted fixes as well without waiting for ActiveState's ppm matrix to test just the alloca functions, so it got left in as a solution.
Memory leak fixed: free'd malloc'd arrays in 2.7