Named Pipes Server


I’ve created a simple named pipes server using overlapped IO.
This server is very similar to Microsoft MSDN sample (using named pipes with
IO completion routines)

The big difference is that instead of returning data immediately to the
client, the server delays the response for about 2 seconds.

After connecting to the server very rapidly from several clients for some
time I’ve noticed that
the process non paged memory size is growing up to the point where the
server was out of physical memory.

Is there a known issue with named pipes and non paged memory?
Am I the only one to face such a problem?

Eitan Michaelson.