Robbie, Thank you for your report.
> It seems that GLPK 4.11 and 4.17 leak a few bytes of > memory each time a problem is built. This may not be a > significant issue, but it is probably worth logging. > The example used was based on sample.c and compiled > using g++. > LEAK SUMMARY: > definitely lost: 0 bytes in 0 blocks. > possibly lost: 0 bytes in 0 blocks. > still reachable: 124 bytes in 1 blocks. > suppressed: 0 bytes in 0 blocks. This is not a bug. That memory block, which remains allocated, is the glpk library environment block; it is automatically allocated by the routine lib_init_env on the first call to any glpk api routine. It can be deallocated by the routine lib_free_env, which frees all resources used by glpk, however, normally this is not needed. This would be needed only in two cases: i) in a multi-threaded environment on terminating the thread, and ii) on processing SIGABORT signal. Andrew Makhorin _______________________________________________ Bug-glpk mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-glpk
