Avoiding Memory Leaks With Pulsewaves

[Spencer Fleming]

Hello!

I'm using this library to help with a project at Boise State. Currently, the program I'm working on has some pretty massive memory leaks that seem to stem from the allocations made when a file is opened with the pulsereader, and they grow exponentially with the file's size. When the program is finished running, it closes and deletes the pulsereader like in the example code, but I'm still left with a lot of memory still allocated. I'm wondering if anyone else has encountered this problem before, or if this is a known issue, or any tips anyone has. It might help point me in the right direction at least.

I'm attaching the output Valgrind gives me-- I apologize if this doesn't seem like enough information.

Thanks!