I'm looking for a program to view and browse the (local) shared memory in Windows x32/x64.
I know this exists because I've seen it in action before. For some reason Google and MSDN fail me on this one.
Windows operating systems provide shared memory using memory backed by the paging file but the lifetime semantics are different from the ones defined by POSIX (see Native windows shared memory section for more information). Some UNIX systems don't fully support POSIX shared memory objects at all.
On Windows: You can use Microsoft Process Explorer to check the shared memory handle of saposcol and then try to find if another process holds it. You should see that some disp+work has the handle. Kill this and then you should be able to stop saposcol and clean the memory.
I think Accesschk can do this.
From the commandline: accesschk.exe -osv > objects.txt
Search for: "Type: Section"
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With