NGen introduces instability
- From: "Bill" <pudchuck@xxxxxxxxx>
- Date: 5 Dec 2006 06:24:17 -0800
We have a section of code that executes cleanly until that code is
NGen'ed. After a native image has been created, that same section of
code produces a .NET Runtime Fatal Execution Engine Failure and the
application closes without warning.
Here is the error for the Event Viewer: .NET Runtime version
2.0.50727.42 - Fatal Execution Engine Error (7A05E2B3) (80131506)
We've re-created this issue on XP, Win2000, and Win2003. We've executed
the native image in the debugger; however the debugger does not produce
anything insightful.
Has anyone else encountered this?
Thank you for your time,
Bill O'Neill
.
- Follow-Ups:
- Re: NGen introduces instability
- From: Damien
- Re: NGen introduces instability
- Prev by Date: Re: Requesting http from a web-site or a windows application, is there any preformance difference?
- Next by Date: Extracting resources ...
- Previous by thread: Requesting http from a web-site or a windows application, is there any preformance difference?
- Next by thread: Re: NGen introduces instability
- Index(es):
Relevant Pages
|
Loading