Freeing wired memory

William A. Mahaffey III wam at hiwaay.net
Fri Oct 10 15:14:56 UTC 2014


On 10/10/14 09:29, Daniel Corbe wrote:
> 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.
>
> -Daniel
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>


What CLI command (if any) did you use to get those memory stats ? TIA ....


-- 

	William A. Mahaffey III

  ----------------------------------------------------------------------

	"The M1 Garand is without doubt the finest implement of war
	 ever devised by man."
                            -- Gen. George S. Patton Jr.



More information about the freebsd-questions mailing list