This article describes hotfix rollup 3139555, 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 Web Installer is a small package (smaller than one megabyte) that automatically determines and downloads only the components that apply to a particular platform.
Resolution
Download information
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 go to 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.
Note To verify the hotfix rollup version after installation, check the value of the Release DWORD value. To be forward-compatible, look for a value that's greater than or equal to the value that's listed in the following table.
|
Hotfix Rollup Version |
Value of the Release DWORD |
|---|---|
|
Hotfix rollup 3139555 for the .NET Framework 4.5 and later versions |
380026 |
For more information about how to determine .NET Framework versions, see How to determine which .NET Framework versions are installed.
Prerequisites
To apply this hotfix, you must have the .NET Framework 4.5.2, 4.5.1, or 4.5 installed.
Restart requirement
You have to restart the computer after you apply this hotfix if any affected files are being used. We recommend that you exit 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
Issue 1
When you run an application that handles heavy workloads that have a specific usage pattern for dynamic methods (for example, Entity Framework and LINQ to SQL), you may experience intermittent crashes in your application.
This issue occurs because of a problem in dynamic method lifetime management. When this issue occurs, System.Reflection.TargetInvocationException is thrown.
This fix corrects the lifetime management problem.
Issue 2
Both System.Web.Caching and System.Runtime.Caching report the size of memory that's used by the whole AppDomain instead of the size of memory that's used by the cache items. This is a regression from the .NET Framework 4.5 because of a change in the Timer implementation. In addition to reporting the incorrect size, the additional objects that are 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 app domains (as reported through the Cache % Process Memory Limit Used ASP.NET performance counter) when app domains are recycled.
This fix removes unintended references from the cache to the other app domain objects so that the correct size is reported. This fix also includes changes to improve the latency for System.Runtime.Caching on multi-core computers that are using Server GC. Additionally, after this fix is applied, the size of all caches in app domain recycling scenarios is calculated correctly.
