.NET Framework 4.6 and RyuJIT (64-bit) critical bug follow-up

This is a follow-up to my previous post.

In a blog post, Rich Lander of the .NET engineering team, acknowledge the bug found by the StackOverflow team and their workaround.  He also says that a patch is on it's way.  It's unlikely that you'll experience this bug but it's always better to be aware.

From the blog post:

This issue is narrow in nature. Your code has to use specific data types, pass them in specific ways and execute specific operations. Very few programs will satisfy all of these characteristics, which is required to trigger this codgen bug.

The .NET team has concluded a detailed analysis of tens of thousands of test assets and internal customer data. The data suggests that the vast majority of .NET developers will not experience this same issue. We have extensive tests for the .NET Framework libraries (e.g. System.Xml). We have not been able to find a single case of this issue across that very large body of code. From a production standpoint, big Microsoft web properties have been running on pre-release versions of .NET Framework 4.6 for months without hitting this issue.

This bug requires a significant set of conditions that must be present to trigger it. It's unlikely that many developers have actually written matching code. We recognize that this bug is very real to StackExchange, and conclude that they are one of the few cases that have and will hit it.

blog comments powered by Disqus

Page List

Month List