Re: NGen introduces instability
- From: "Damien" <Damien_The_Unbeliever@xxxxxxxxxxx>
- Date: 5 Dec 2006 07:50:05 -0800
Bill wrote:
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'Neil
I'm guessing it's the variable called "blarg", on line 32.
You say you've reproduced this on XP, 2000 and 2003. Can you produce a
simple sample piece of code that exhibits this problem, or can you only
reproduce it with your full solution.
It's a *lot* easier to diagnose problems when we have code in front of
us.
Damien
.
- Follow-Ups:
- Re: NGen introduces instability
- From: Bill
- Re: NGen introduces instability
- References:
- NGen introduces instability
- From: Bill
- NGen introduces instability
- Prev by Date: Extracting resources ...
- Next by Date: Re: Requesting http from a web-site or a windows application, is there any preformance difference?
- Previous by thread: NGen introduces instability
- Next by thread: Re: NGen introduces instability
- Index(es):
Relevant Pages
|
