[Symphony-tickets] [SYMPHONY] #141: Segfaults in 5.6.8/ Memory leaks in sym_get_row_activity and str_br_bound_changes in 5.6.5

[SYMPHONY]

#141: Segfaults in 5.6.8/ Memory leaks in sym_get_row_activity and
str_br_bound_changes in 5.6.5
----------------------+-----------------
 Reporter:  troost_c  |      Owner:  tkr
     Type:  defect    |     Status:  new
 Priority:  normal    |  Milestone:  5.2
Component:  Not Sure  |    Version:
 Keywords:            |
----------------------+-----------------
 Dear SYMPHONY team,

 we are using SYMPHONY version 5.6.5 in an application that solves
 thousands of MIP problems, one after the other. To check for potential
 memory leakages, I ran our application through valgrind. It reports two
 sources of leakages:

 1) In sym_get_row_activity the memory allocated for colsol (master.c: line
 3368) is never freed.

 2) In str_br_bound_changes memory is allocated in (lp_genfunc: 1775-1778)
 is also at least sometimes not freed.

 As far as I could see (and in the first case I am pretty sure), I as a
 user cannot explicitly free that memory. Correct me if I am wrong.

 I tried the latest version 5.6.8: but there the
 OsiSymSolverInterface::getRowActivity() function I am using (and which
 leads to problem 1) has been changed and I get a segmentation fault in
 sym_get_row_activity (when memsetting on rowactivity), because
 sym_get_row_activity is called on rowact_ in the if condition though no
 memory has been allocated for rowact_ yet.

 Could you check and correct both segfault and memory leaks?
 Thank you.

 Best,
 Christian

--
Ticket URL: <https://projects.coin-or.org/SYMPHONY/ticket/141>
SYMPHONY <http://projects.coin-or.org/SYMPHONY>
The SYMPHONY framework for parallel branch-and-cut algorithms.