This article describes hotfix rollup 3139544, which is available for the Microsoft .NET Framework 4.5.2, 4.5.1, and 4.5. For more information about the fixes in this hotfix rollup, see the Issues that this hotfix rollup fixes section.
The Offline Installer can be used when you don't have Internet connectivity and cannot use the Web Installer. Wherever possible, we recommend that you use the Web Installer instead of the Offline Installer for optimal efficiency and bandwidth requirements.
The following file is available for download from the Microsoft Download Center:
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
To apply this hotfix, you must have the .NET Framework 4.5.2, the .NET Framework 4.5.1, or the .NET Framework 4.5 installed.
You have to restart the computer after you apply this hotfix if any affected files are being used. We recommend that you close all .NET Framework-based applications before you apply this hotfix.
Hotfix replacement information
This hotfix package doesn't replace a previously released hotfix package.
Issues that this hotfix rollup fixes
Large workloads that have a specific usage pattern for dynamic methods (such as LINQ to SQL and the Entity Framework) encounter an intermittent crash that's caused by an issue in dynamic method lifetime management. This fix will help you correct the lifetime management issue.
Both System.Web.Caching and System.Runtime.Caching incorrectly report the size of memory used by the whole AppDomain instead of the size of memory used by the cache items. This is a regression issue from the .NET Framework 4.5 in which a change in Timer implementation was made. IN addition to reporting an incorrect size, the additional objects referenced by the cache may significantly affect Gen2 GC latency. In ASP.NET hosting scenarios, the cache also miscalculates the size of all caches in all application domains (reported through the Cache % Process Memory Limit Used ASP.NET performance counter) when application domains are recycled.
This fix removes unintended references from the cache to the rest of the application domain objects. It also includes changes to improve latency for System.Runtime.Caching on multi-core systems by using Server GC. Finally, this fix correctly calculates the size of all caches in application domain recycling scenarios.