Potential memory leak in ensure_column_capacity due to unsafe realloc usage
#1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
I found a potential memory leak in
ensure_column_capacitywhen handlingreallocfailures.Root cause
In the current implementation, the results of
reallocare assigned directly tostate->objective_coeffs,state->var_lower_bounds, andstate->var_upper_bounds. If onereallocsucceeds but a later one fails, the original pointer is lost,causing a memory leak.
Suggested fix
Use temporary variables for each
realloccall, only assign back if all succeed, and free any partially allocated blocks on failure. I implemented a fix in my fork.Impact
No functional change in normal cases. The fix only improves robustness in low-memory conditions by preventing leaks.
Testing
Pass the test with
2club200v15p5scn.mps.gzinstance.