jerasure backend leaks memory on exit
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
liberasurecode |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Both jerasure_rs_vand and jerasure_rs_cauchy can leak the allocated memory at the exit as valgrind memory check can report it.
The allocated memory is at static area and it should happen only once (for a single thread case) because the area will be allocated only it's not yet so that I don't think it's problematic on the running processes like OpenStack Swift services. Therefore we can triage this bug only in liberasurecode (or perhaps +jerasure or +pyeclib?) world.
As described above, jerasure often touches memory allocated to the static area so we have to free it once we leave the process even if we don't allocate it intentionally.
On the perspective that the memory is at static area, we may have to consider the multithreading case (racing to allocate the memory) on either jerasure or liberasurecode (, or user client?).
Changed in liberasurecode: | |
status: | New → Fix Committed |
Changed in liberasurecode: | |
status: | Fix Committed → Fix Released |
The fix is proposed at https:/ /review. openstack. org/#/c/ 434696