2011-08-30 03:38:13 |
Tim Penhey |
bug |
|
|
added bug |
2011-09-30 14:50:49 |
Didier Roche-Tolomelli |
unity (Ubuntu): status |
New |
Confirmed |
|
2012-04-02 06:48:17 |
Ritesh Khadgaray |
bug |
|
|
added subscriber Ritesh Khadgaray |
2012-06-13 23:51:02 |
Thomi Richards |
attachment added |
|
Small app to reproduce the issue. https://bugs.launchpad.net/unity/+bug/837145/+attachment/3188605/+files/pango_leak.c |
|
2012-06-13 23:52:37 |
Robert Ancell |
bug task added |
|
pango1.0 (Ubuntu) |
|
2012-06-14 00:42:41 |
Robert Ancell |
bug watch added |
|
https://bugzilla.gnome.org/show_bug.cgi?id=678059 |
|
2012-06-14 00:42:41 |
Robert Ancell |
bug task added |
|
pango |
|
2012-06-14 01:18:53 |
Bug Watch Updater |
pango: status |
Unknown |
New |
|
2012-06-14 01:18:53 |
Bug Watch Updater |
pango: importance |
Unknown |
Medium |
|
2012-06-14 01:25:36 |
Launchpad Janitor |
pango1.0 (Ubuntu): status |
New |
Fix Released |
|
2012-06-14 11:18:32 |
Omer Akram |
unity: status |
Confirmed |
Invalid |
|
2012-06-14 11:18:34 |
Omer Akram |
unity (Ubuntu): status |
Confirmed |
Invalid |
|
2012-06-14 22:13:59 |
Robert Ancell |
description |
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. |
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:
- TODO
...
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. |
|
2012-06-14 22:15:57 |
Robert Ancell |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2012-06-15 01:28:49 |
Bug Watch Updater |
pango: status |
New |
Fix Released |
|
2012-06-19 03:37:50 |
Scott Kitterman |
nominated for series |
|
Ubuntu Precise |
|
2012-06-19 03:37:50 |
Scott Kitterman |
bug task added |
|
pango1.0 (Ubuntu Precise) |
|
2012-06-19 03:37:50 |
Scott Kitterman |
bug task added |
|
unity (Ubuntu Precise) |
|
2012-06-19 03:38:04 |
Scott Kitterman |
pango1.0 (Ubuntu Precise): status |
New |
In Progress |
|
2012-06-19 03:38:08 |
Scott Kitterman |
unity (Ubuntu Precise): status |
New |
Invalid |
|
2012-07-03 04:23:26 |
Tim Penhey |
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:
- TODO
...
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. |
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. |
|
2012-07-03 04:43:28 |
Chris Halse Rogers |
pango1.0 (Ubuntu Precise): status |
In Progress |
Fix Committed |
|
2012-07-03 04:43:33 |
Chris Halse Rogers |
bug |
|
|
added subscriber SRU Verification |
2012-07-03 04:43:40 |
Chris Halse Rogers |
tags |
memory-leak |
memory-leak verification-needed |
|
2012-07-09 20:36:27 |
Sebastien Bacher |
tags |
memory-leak verification-needed |
memory-leak verification-done |
|
2012-07-10 17:54:59 |
Launchpad Janitor |
pango1.0 (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
2012-08-09 18:48:12 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/pango1.0 |
|
2012-08-09 18:48:17 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/ubuntu/precise/pango1.0/precise-proposed |
|
2012-11-12 16:46:50 |
Launchpad Janitor |
branch linked |
|
lp:debian/experimental/pango1.0 |
|
2012-11-13 13:21:35 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/pango1.0 |
|