System status:
The application memory:
Poolmon state (according to NonPage take up from order of the) :
The page buffer Pool there Pool (N) has a value of about 60 g, but the list, the biggest only 426 m, the page buffer Pool is no problem,
System running our c + + applications, is to use the new application memory, can't touch the page buffer pool this, but call the lens, the sea Kang Dahua SDK connections that up until now have run out of memory and need to restart the machine to solve it, if is the problem that the SDK, I should how to debug to find out the evidence, because see his exe related memory are normal,
The page buffer pool not suddenly rose, but irregular rose slowly, the machine run for a month or so,
Don't know how to debug, now, is there a way how to see who was eating the page buffer pool memory?
CodePudding user response:
Using multiple process isolation resource leaks,CodePudding user response: