This issue is resolved in the following ESX/ESXi releases:
Note: This issue does not affect ESXi 5.1
If you are unable to upgrade to the appropriate release, to workaround this issue on earlier release of ESX/ESXi, reboot the host. Rebooting the host restarts the counter and eliminates the risk of any failure.
To avoid a reboot, you can check to determine if your system is at risk.
To determine if your system is at risk, run this script in the ESXi command line:
ps -c | awk {'print $1'} | sort -n | tail -n 1
If the output returns a value of 100,000 or above it is recommended to schedule a reboot.