I also did some more testing for memory leaks using Valgrind which is not infallible but a good indication of incorrect memory usage patterns and while I did find a small memory leak in the presentation view (a few bytes at most) there seem to be no serious memory leaks in the qpdfview code base.
I also did some more testing for memory leaks using Valgrind which is not infallible but a good indication of incorrect memory usage patterns and while I did find a small memory leak in the presentation view (a few bytes at most) there seem to be no serious memory leaks in the qpdfview code base.