Open GoogleCodeExporter opened 9 years ago
Original comment by alkondratenko
on 6 Jul 2013 at 11:16
The memory leak had been found to be a Qt bug in fbo(frame buffer object) pool
implementation.
The is due to the software OpenGL driver(the machine has no real graphics gpu
hardware) which doesn't support `multi-sample` feature.
My question is: why does HEAPCHECK tool fail in this situation?
Original comment by ctengc...@gmail.com
on 9 Jul 2013 at 1:34
Valgrind can work in this situation, but it only found a lot of small
"possible" leaks which were in fact not related.
I've an idea: could HEAPCHECK tool only check memory blocks which size is >
given threshold? For wasting extra memory recording small-size blocks is no
useful.
Original comment by ctengc...@gmail.com
on 9 Jul 2013 at 1:39
> I've an idea: could HEAPCHECK tool only check memory blocks which size is >
given threshold? For wasting extra memory recording small-size blocks is no
useful.
If you contribute such change we'll gladly accept it :)
Original comment by alkondratenko
on 24 Jul 2013 at 5:10
Original issue reported on code.google.com by
ctengc...@gmail.com
on 19 Jun 2013 at 8:42