Yes, it is true that I have not reported this before. We just recently upgraded to the newest version of NUnit from a much older version due to the need to support .NET 4.0.
I get a popup and the event log gives me the following description:
"Application popup: nunit-agent-x86.exe - Application Error : The instruction at "0x7c82a82f" referenced memory at "0x4ba1dff4". The memory could not be "written".
Click on OK to terminate the program"
The environment is a Windows 2003 R2 OS. I'm executing this command by command console, invoking nant which then calls nunit-console-x86.exe. What's strange about this is that it comes up inconsistently... so much so that running it up to 10 times may not produce the issue for me. Further, I attempted to run the x86 console directly and was unable to reproduce the issue after several attempts, but I can't be sure that I simply didn't try it enough.
It seems plausible that the issue is environmental, but it seems rather similar to the problem here. Is there any further way that I might be able to diagnose the issue? Logs? Anything I've missed that may be of value?
Charlie,
Yes, it is true that I have not reported this before. We just recently upgraded to the newest version of NUnit from a much older version due to the need to support .NET 4.0.
I get a popup and the event log gives me the following description:
"Application popup: nunit-agent-x86.exe - Application Error : The instruction at "0x7c82a82f" referenced memory at "0x4ba1dff4". The memory could not be "written".
Click on OK to terminate the program"
The environment is a Windows 2003 R2 OS. I'm executing this command by command console, invoking nant which then calls nunit-console- x86.exe. What's strange about this is that it comes up inconsistently... so much so that running it up to 10 times may not produce the issue for me. Further, I attempted to run the x86 console directly and was unable to reproduce the issue after several attempts, but I can't be sure that I simply didn't try it enough.
It seems plausible that the issue is environmental, but it seems rather similar to the problem here. Is there any further way that I might be able to diagnose the issue? Logs? Anything I've missed that may be of value?