Control: tags -1 + moreinfo On 2016-01-05 14:23:20, gi1242+debianb...@gmail.com wrote: > Update: I ran valgrind. Here's the summary: > > ==13647== LEAK SUMMARY: > ==13647== definitely lost: 274,913 bytes in 62 blocks > ==13647== indirectly lost: 29,937 bytes in 1,264 blocks > ==13647== possibly lost: 71,528 bytes in 876 blocks > ==13647== still reachable: 70,136,419 bytes in 31,730 blocks > ==13647== suppressed: 0 bytes in 0 blocks > ==13647== Reachable blocks (those to which a pointer was found) are not > shown. > ==13647== To see them, rerun with: --leak-check=full --show-leak-kinds=all > > Looks like there definitely is a memory leak which leaks sizable chunks > of memory (not just a KB or two).
Unfortunately that information is not useful. Without knowing where it exactly leaks, we can not do very much. I'd recommend to try the new version available in unstable and check if the problem still exists. Otherwise we need a more verbose valgrind log with the GTK+ leaks filtered out. Cheers -- Sebastian Ramacher
signature.asc
Description: PGP signature
