Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Oct 2014 10:29:20 -0400
From:      Daniel Corbe <>
Subject:   Freeing wired memory
Message-ID:  <>

Next in thread | Raw E-Mail | Index | Archive | Help

There's an application running on one of my hosts which has a memory
leak in it.  It ends up consuming a fair chunk of available RAM:

Mem: 2312M Active, 69M Inact, 13G Wired, 39M Cache, 1684M Buf, 354M Free

My understanding is Wired memory is memory that may not necessarily be
in use but it is reserved for applications that either have at one point
needed it or may need it in the future.

I'll kill the app in another few days or so because calls to malloc()
will begin to fail across the board.  

But my main problem right now is I usually have to reboot the box
because killing the app and restarting it does NOT return any memory to
the free pool.

The step I'd like to avoid here is rebooting the box.

So I'm obviously missing something.


Want to link to this message? Use this URL: <>