I have a NAT program that crashes inside the CLR JIT More out-of-memory errors, but only when a power shell moves from inside the job . I am assuming that it is running as a powerful job as a run of some kind of resource or security limitations which leads to the .NET CLR nuts. The most obvious clue was able to achieve that one exception was HRESULT, which HRESULT ERROR_COMMITMENT_LIMIT (pagefile was exhausted) once revealed itself as one of those errors, although in the pagefile actually There were lots of rooms and for the second time in RAM, these errors are completely arbitrary and innocent in the program. How can I squeeze out what's going wrong, what limit is being violated? ? Is there an API to achieve all restrictions which is under any process? Or is there a way to block or log a Winipi call that fails due to security or quota restrictions? I'm fine with using WinDbg for this too, but I do not know how to use it for this task. It is unlikely that PowerShell is here at fault, it does not apply any security or CLR modifications. That is, that the hair processes are passed which makes it. One item PowerShell will definitely be passed to the hair process environment variable. It is very possible that PowerShell CMD, which is affecting CLR or your program and causing it to crash, a different environment Passing through variable. I will start a CMD and PowerShell session and will exclude their environment variables to exclude it as a reason. Specifically I would like to focus on the % PATH% variable
Comments
Post a Comment