Can "\Device\NamedPipe\\Win32Pipes" handles cause "Too many open files" error?

Posted by Igor Oks on Stack Overflow See other posts from Stack Overflow or by Igor Oks
Published on 2010-03-15T11:08:13Z Indexed on 2010/03/15 11:09 UTC
Read the original article Hit count: 274

Filed under:
|
|
|

Continuing from this question:

When I am trying to do fopen on Windows, I get a "Too many open files" error. I tried to analyze, how many open files I have, and seems like not too much.

But when I executed Process Explorer, I noticed that I have many open handles with similar names: "\Device\NamedPipe\Win32Pipes.00000590.000000e2", "\Device\NamedPipe\Win32Pipes.00000590.000000e3", etc. I see that the number of these handles is exactly equal to the number of the iterations that my program executed, before it returned "Too many open files" and stopped.

I am looking for an answer, what are these handles, and could they actually cause the "Too many open files" error?

In my program I am loading files from remote drive, and I am creating TCP/IP connections. Could one of these operations create these handles?

© Stack Overflow or respective owner

Related posts about file

Related posts about handle