What steps will reproduce the problem?
1. Write a program that uses dynamic vertex data.
2. Run it on a big graph with many iterations (depends on the size of the graph
and the available memory).
3. Observe the segfault that is caused by the memory leak.
What is the expected output? What do you see instead?
Our code ran on a graph with about 5000 vertices. We have discovered two memory
leaks:
- at dynamicblock.hpp:106, which resulted in a loss of 37MB (valgrind.1)
- at graphchi_engine.hpp:992, which leaked about 230kB (valgrind.2)
What version of the product are you using? On what operating system?
Latest trunk.
Please provide any additional information below.
I have attached our fixes (patch).
Original issue reported on code.google.com by nda...@sztaki.hu on 16 Jul 2013 at 3:05
Original issue reported on code.google.com by
nda...@sztaki.hu
on 16 Jul 2013 at 3:05Attachments: