Up to date valgrind and testing for leaks

Bug #610389 reported by Karl Lattimer on 2010-07-27
This bug affects 4 people
Affects Status Importance Assigned to Milestone
notify-osd (Ubuntu)

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.

Karl Lattimer (karl-qdh) on 2010-07-27
Changed in notify-osd:
assignee: nobody → Karl Lattimer (karl-qdh)
Karl Lattimer (karl-qdh) on 2010-07-27
Changed in notify-osd:
importance: Undecided → Medium
Karl Lattimer (karl-qdh) wrote :

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.

David Barth (dbarth) on 2010-09-01
Changed in notify-osd:
assignee: Karl Lattimer (karl-qdh) → nobody
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

affects: notify-osd → notify-osd (Ubuntu)
Changed in notify-osd (Ubuntu):
status: New → Confirmed
Changed in notify-osd (Ubuntu):
status: New → Confirmed
Matthew Carpenter (matt-eisgr) wrote :

Still leaking. I'm at 5.9gb and I just rebooted a few hours ago.
I had turned off KDE Notifications because plasma-shell was growing to huge amounts of RAM usage... so I wonder if there is some connection?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions