Hello Tim, or anyone else affected, Accepted pango1.0 into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/pango1.0/1.30.0-0ubuntu3.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: pango1.0 (Ubuntu Precise) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/837145 Title: Memory leak in pango_layout_get_extents Status in Pango - Layout and Text Rendering LIbrary: Fix Released Status in Unity: Invalid Status in “pango1.0” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “pango1.0” source package in Precise: Fix Committed Status in “unity” source package in Precise: Invalid Bug description: Impact: there is a memory leak when using pango_layout_get_extents Development Fix: the bug has been fixed in quantal Stable Fix: simple patch accepted upstream at https://bugzilla.gnome.org/show_bug.cgi?id=678059 Regression Potential: could potentially cause other bugs Test Case: - Run the following code in a terminal (feel free to check the result of the GET first) {{{ for size in 100 200 500; do echo With size $size GET https://bugzilla.gnome.org/attachment.cgi?id=216360 | sed s/100/$size/ > pango_leak.c gcc pango_leak.c `pkg-config --cflags --libs pangoft2` -o pango_leak valgrind ./pango_leak 2>&1 | grep ' lost' | cut -d" " -f 2- done; }}} Observe that before the fix the possibly lost reported grows significantly which different loop counts, and that after the fix it does not. -- End test case Valgrind found a leak deep in the nested calls for 'pango_layout_get_extents'. It appears to be not freeing something. 4,224 (512 direct, 3,712 indirect) bytes in 1 blocks are definitely lost 1,904 (768 direct, 1,136 indirect) bytes in 1 blocks are definitely lost 1,904 (768 direct, 1,136 indirect) bytes in 1 blocks are definitely lost This from an hour long valgrind run. To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/837145/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
