what is the system defined amount for this (and other similar events) to trigger ?
REF: http://msdn.microsoft.com/en-us/library/windows/hardware/ff563847(v=vs.85).aspx
Purposefully not defined to a specific number as that can change at any time depending on what the OS feels is a low memory condition
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Friday, September 7, 2012 10:10 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] \KernelObjects\LowMemoryCondition
what is the system defined amount for this (and other similar events) to trigger ?
REF: http://msdn.microsoft.com/en-us/library/windows/hardware/ff563847(v=vs.85).aspx
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
So when does OS feels it is a low memory condition ? On my machine of 4GB RAM, this event is triggered when the task manager shows mem usage as ~2.75GB.
What Doron said.
I would add that I’ve never observed the event named in the subject line set on XP through Server 2008 R2, even when intentionally running the system out of memory.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Friday, September 07, 2012 11:15 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] \KernelObjects\LowMemoryCondition
Purposefully not defined to a specific number as that can change at any time depending on what the OS feels is a low memory condition
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Friday, September 7, 2012 10:10 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] \KernelObjects\LowMemoryCondition
what is the system defined amount for this (and other similar events) to trigger ?
REF: http://msdn.microsoft.com/en-us/library/windows/hardware/ff563847(v=vs.85).aspx
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
My observation is on a win 7, 64-bit machine.
You can check the current value of the threshold, and how many pages are actually available, using these debugger commands:
dp nt!MmLowMemoryThreshold l1
dp nt!MmAvailablePages l1
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Friday, September 7, 2012 10:41 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] \KernelObjects\LowMemoryCondition
So when does OS feels it is a low memory condition ? On my machine of 4GB RAM, this event is triggered when the task manager shows mem usage as ~2.75GB.
Depending on how exactly you consume memory you can run out of commit, address space or some other resource before you run out of physical pages.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Phil Barila
Sent: Friday, September 7, 2012 10:41 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] \KernelObjects\LowMemoryCondition
What Doron said.
I would add that I’ve never observed the event named in the subject line set on XP through Server 2008 R2, even when intentionally running the system out of memory.
“”““dp nt!MmLowMemoryThreshold l1
dp nt!MmAvailablePages l1"””"
Thank you Pavel, that helps.
“”“”“Depending on how exactly you consume memory you can run out of commit, address
space or some other resource before you run out of physical pages.”“”“”
And this event \KernelObjects\LowMemoryCondition will still be set if there are physical pages available but no commit/address space ?
That was faulty memory on my part. It never fired on XP, but I used the newer ones on later OS versions. And my method of running it out of memory may not have exhausted PhysicalMemory before the Pools were exhausted.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Pavel Lebedynskiy
Sent: Friday, September 07, 2012 1:22 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] \KernelObjects\LowMemoryCondition
Depending on how exactly you consume memory you can run out of commit, address space or some other resource before you run out of physical pages.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Phil Barila
Sent: Friday, September 7, 2012 10:41 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] \KernelObjects\LowMemoryCondition
What Doron said.
I would add that I’ve never observed the event named in the subject line set on XP through Server 2008 R2, even when intentionally running the system out of memory.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
> And this event \KernelObjects\LowMemoryCondition will still be set if there are physical pages available but no commit/address space ?
No, LowMemoryCondition is specifically for physical memory. There are separate events for commit and pool usage. There is no event for the overall kernel VA space usage.