Public bug reported:
Valgrind reports that so many bytes have leaked when a gtk program is
run.
Steps to reproduce:
1. Compile a simple gtk code involving a label.
2. run valgrind --leak-check=full ./<program name>
Actual results:
result:
==15510== LEAK SUMMARY:
==15510== definitely lost: 10,058 bytes in 43 blocks.
==15510== indirectly lost: 22,576 bytes in 1,118 blocks.
==15510== possibly lost: 71,896 bytes in 68 blocks.
==15510== still reachable: 1,026,782 bytes in 7,611 blocks.
==15510== suppressed: 0 bytes in 0 blocks.
Expected results:
There shouldn't be any leak.
Gtk+ version 2.10.11
Gnome version 2.18
Ubuntu Feisty 7.04
See the attachments : the sample gtk code, the valgrind output using
--leak-check=full option
** Affects: gtk+2.0 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
valgrind reports leak of memory even in simple gtk programs
https://bugs.launchpad.net/bugs/114061
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gtk+2.0 in ubuntu.
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
