Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 198
  • Last Modified:

Limitations of no of Handles in Win NT

What is the maximum no of handles Wint NT can access. My applications which access shared memory had caused the number of handles and physical memory as shown on task manager to go up progressively. I did not use the UnMapFileViewing() as my application will crash. What could be the possible cause?
0
ho_cm
Asked:
ho_cm
1 Solution
 
ho_cmAuthor Commented:
The main reason that my application will crash is that there are six threads that will be accessing the shared memory.. but on different location thus does not need any memory locking devices. If I use UnMapFileViewing function, my application will crash as it will be awaiting responses from the shared memory.
0
 
_Scotch_Commented:
I dont know whats crashing your application but I had a threaded
app that was leaking HBRUSHes ...  It would leak over 5000 of
them before the app would get flaky so I think you can safely
access 5000 handles, at least on this box ;)
0
 
rwilson032697Commented:
I think NT provides either 8192 or 16384 handles. I'm not sure which.

Cheers,

Raymond.
0
 
mikeblasCommented:

The number of handles available depends on what the handles actually reference!

B ekiM
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simple Misconfiguration =Network Vulnerability

In this technical webinar, AlgoSec will present several examples of common misconfigurations; including a basic device change, business application connectivity changes, and data center migrations. Learn best practices to protect your business from attack.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now