Up to date valgrind and testing for leaks
Bug #610389 reported by
Karl Lattimer
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| notify-osd (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
As some existing memory leak bugs have long out of date valgrind reports and do not in any way reflect the current codebase they cannot be considered valid any longer. This includes bug #378193 and #405364 both of which have had specific fixes committed.
This bug is intended as a reminder to produce some valgrind reports and collect any intermediate valgrind reports from testing.
| Changed in notify-osd: | |
| assignee: | nobody → Karl Lattimer (karl-qdh) |
| Changed in notify-osd: | |
| importance: | Undecided → Medium |
Revision history for this message
| Karl Lattimer (karl-qdh) wrote | #1 |
| Changed in notify-osd: | |
| assignee: | Karl Lattimer (karl-qdh) → nobody |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| affects: | notify-osd → notify-osd (Ubuntu) |
| Changed in notify-osd (Ubuntu): | |
| status: | New → Confirmed |
| Changed in notify-osd (Ubuntu): | |
| status: | New → Confirmed |
Revision history for this message
| Matthew Carpenter (matt-eisgr) wrote | #4 |
To post a comment you must log in.
The bug #438743 (mem-leak caused by load_icon()) has been merged into this bug. The code near it has changed significantly so the valgrind logs are pretty much useless and the bug might have been fixed.