Mitigation: New 64-bit JIT Compiler
Starting with .NET Framework 4.6, the runtime includes a new 64-bit JIT compiler for just-in-time compilation. This change does not affect compilation with the 32-bit JIT compiler.
Unexpected behavior or exceptions
In some cases, compilation with the new 64-bit JIT compiler results in a runtime exception or in behavior that is not observed when executing code compiled by the older 64-bit JIT compiler. The known differences include the following:
All of these known issues have been addressed in the new 64-bit compiler released with the .NET Framework 4.6.2. Most have also been addressed in service releases of the .NET Framework 4.6 and 4.6.1 that are included with Windows Update. You can eliminate these issues by ensuring that your version of Windows is up to date, or by upgrading to the .NET Framework 4.6.2.
Under certain conditions, an unboxing operation may throw a NullReferenceException in Release builds with optimization turned on.
In some cases, execution of production code in a large method body may throw a StackOverflowException.
Under certain conditions, structures passed to a method are treated as reference types rather than value types in Release builds. One of the manifestations of this issue is that the individual items in a collection appear in an unexpected order.
Under certain conditions, the comparison of UInt16 values with their high bit set is incorrect if optimization is enabled.
Under certain conditions, particularly when initializing array values, memory initialization by the OpCodes.Initblk IL instruction may initialize memory with an incorrect value. This can result either in an unhandled exception or incorrect output.
Under certain rare conditions, a conditional bit test can return the incorrect Boolean value or throw an exception if compiler optimizations are enabled.
Under certain conditions, if an
ifstatement is used to test for a condition before entering a
tryblock and in the exit from the
tryblock, and the same condition is evaluated in the
finallyblock, the new 64-bit JIT compiler removes the
ifcondition from the
finallyblock when it optimizes code. As a result, code inside the
ifstatement in the
finallyblock is executed unconditionally.
Mitigation of known issues
If you encounter the issues listed above, you can address them by doing any of the following:
Upgrade to the .NET Framework 4.6.2. The new 64-bit compiler included with the .NET Framework 4.6.2 addresses each of these known issues.
Ensure that your version of Windows is up to date by running Windows Update. Service updates to the .NET Framework 4.6 and 4.6.1 address each of these issues except the NullReferenceException in an unboxing operation.
Compile with the older 64-bit JIT compiler. See the Mitigation of other issues section for more information on how to do this.
Mitigation of other issues
If you encounter any other difference in behavior between code compiled with the older 64-bit compiler and the new 64-bit JIT compiler, or between the debug and release versions of your app that are both compiled with the new 64-bit JIT compiler, you can do the following to compile your app with the older 64-bit JIT compiler:
On a per-application basis, you can add the <useLegacyJit> element to your application's configuration file. The following disables compilation with the new 64-bit JIT compiler and instead uses the legacy 64-bit JIT compiler.
<?xml version ="1.0"?> <configuration> <runtime> <useLegacyJit enabled="1" /> </runtime> </configuration>
On a per-user basis, you can add a
HKEY_CURRENT_USER\SOFTWARE\Microsoft\.NETFrameworkkey of the registry. A value of 1 enables the legacy 64-bit JIT compiler; a value of 0 disables it and enables the new 64-bit JIT compiler.
On a per-machine basis, you can add a
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFrameworkkey of the registry. A value of 1 enables the legacy 64-bit JIT compiler; a value of 0 disables it and enables the new 64-bit JIT compiler.
You can also let us know about the problem by reporting a bug on Microsoft Connect.