What to do to get a fix in 8.04?

Chris Mohler cr33dog at gmail.com
Fri Oct 31 02:30:32 UTC 2008

On Thu, Oct 30, 2008 at 9:26 PM, NoOp <glgxg at sbcglobal.net> wrote:
> On 10/30/2008 07:06 PM, Chris Mohler wrote:
>> On Thu, Oct 30, 2008 at 8:47 PM, NoOp <whydopeopleuseprogramsthatincludetheemailaddresshere?> wrote:
>>>>>Given that Hardy is an LTS, I see the requirement to apply the fix to
>>>>>hardy as considerably more important than Intrepid. But the last post on
>>>>>that bug indicates that it's not fixed in Intrepid either.
>>>>>Does anyone know of a good memory leak detection manager that could be
>>>>>used to effectively monitor this?
>>>> top and then sort for memory (M).
>>> Yeah, but that doesn't work well for logging and providing details for
>>> what/where/when etc., that I know of. I'd prefer to find a way to dump
>>> memory leaks to a file (similar to the Mozilla SeaMonkey 'Leak Detector'
>>> in 2.0a1) so that the information can be added to a bug report.
>> How about valgrind?
>> Chris
> That might work: https://wiki.ubuntu.com/Valgrind
> Any idea how you start it to automatically monitor NM?

Killing nm and then restarting manually should work.

The other option I can think of is modifying the nm init script to run
via valgrind and log it somewhere.


More information about the ubuntu-users mailing list