Bug#557301: libimlib2-dev: imlib_load_image contains a memleak

2018-02-06 Thread Markus Koschany
Am 06.02.2018 um 11:03 schrieb Alexander Volkov: > I tested it with imlib2 1.4.10, there is no memleak: Thank you very much for investigating this issue. I'll double-check it and intend to close this bug report eventually. Regards, Markus

Bug#557301: libimlib2-dev: imlib_load_image contains a memleak

2018-02-06 Thread Alexander Volkov
I tested it with imlib2 1.4.10, there is no memleak: ==2591== Memcheck, a memory error detector ==2591== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==2591== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==2591== Command: ./a.out ==2591== ==2591== ==2591==

Bug#557301: libimlib2-dev: imlib_load_image contains a memleak

2009-11-20 Thread Nikolas Garofil
Package: libimlib2-dev Version: 1.4.2-5 Severity: normal *** Please type your report below this line *** If you write a program using imlib_load_image() or similar functions, you will notice a memleak when you run the program in valgrind. imlib_load_image calls imlib_context_push and imlib_context