I'm having issues with Dsp on a fairly large graph.
If I run several rounds of dsp with different sources and targets in the same session, the postgresql process memory keeps growing, until the OOM killer gets rid of it.
If I just close the session everytime, memory stays at a reasonable level.
I tried looking at the source code, but maybe I need some guidance in where to look at.
I can provide some sort of dataset, if it helps.
I should add: I'm currently using github master branch.
I tried to free the malloc()ed vector in the boost wrapper after copying it to a palloc()ed vector, but no improvement. Postgres is still blowing
I was trying to fix this problem a long time ago, but I coudn´t.
I think the right way to fix this is calling palloc (c postgresql function) instead malloc from c++ code in the source code:
*path = (path_element_t *) malloc(sizeof(path_element_t) * (path_vect.size() + 1));
but I do not know exactly how to do this, if you can understand this:
surely you can fix it!
I have merged pull request #67 into branch sew-devel-2_0.
Closing - Wont fix.