How to interpret ::kmastat to check if the kernel is leaking memory

(Doc ID 1011469.1)

Last updated on MAY 17, 2018

Applies to:

Solaris Operating System - Version 10 3/05 and later
All Platforms


Large numbers in the "memory in use" column in mdb's ::kmastat output are often cause for concern. This document explains the conditions under which these concerns may be legitimate.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms