Is there any way to tell which /dev/shmem entries are associated
with which process? I’m thinking that the number of /dev/shmem
entries keeps growing and that I may have a memory leak, but I’m
hard pressed to figure out which one is owned by what… Any
suggestions/tricks?
Cheers,
-RK
–
[If replying via email, you’ll need to click on the URL that’s emailed to you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector http://www.parse.com/~pdp8/
“Robert Krten” <rk@parse.com> wrote in message
news:ch2rje$hcf$1@inn.qnx.com…
Is there any way to tell which /dev/shmem entries are associated
with which process? I’m thinking that the number of /dev/shmem
entries keeps growing and that I may have a memory leak, but I’m
hard pressed to figure out which one is owned by what… Any
suggestions/tricks?
The ones created by the Photon library follow a simple naming convention:
“Pg%04x%04x”, pid & 0xFFFF, serial_num
Wojtek Lerch <Wojtek_L@yahoo.ca> wrote:
“Robert Krten” <> rk@parse.com> > wrote in message
news:ch2rje$hcf$> 1@inn.qnx.com> …
Is there any way to tell which /dev/shmem entries are associated
with which process? I’m thinking that the number of /dev/shmem
entries keeps growing and that I may have a memory leak, but I’m
hard pressed to figure out which one is owned by what… Any
suggestions/tricks?
The ones created by the Photon library follow a simple naming convention:
“Pg%04x%04x”, pid & 0xFFFF, serial_num
Thanks. I had been accumulating Pg… entries in /dev/shmem and leaking
memory. I’m not 100% convinced it was any of my utilities, so I’ll investigate
a bit more before pointing fingers 
Cheers,
-RK
–
[If replying via email, you’ll need to click on the URL that’s emailed to you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector http://www.parse.com/~pdp8/