Wrong information when querying 64-bit process memory usage from 32-bit process - by Luboš Kresta

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 767083 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 10/11/2012 11:11:46 AM
Access Restriction Public

Description

When querying System.Diagnostics.Process.PrivateMemorySize64 for a 64-bit process from 32-bit process, the maximum value reported is 4294967295 (2^32 - 1), even if actual memory usage of the process is higher. When querying the same information from 64-bit process, the value returned is correct.
Sign in to post a comment.
Posted by Microsoft on 2/22/2013 at 2:44 PM
Thank you Lubos for raising the issue to our attention.

Unfortunately, we are unable to implement the fix for this problem in the current version of .NET 4.5. We are however, keeping the bug so that we can consider it in a future version of the product. Thank you for reporting.
Posted by Macy [MSFT] on 10/16/2012 at 4:19 AM
Thanks for your update. We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Luboš Kresta on 10/12/2012 at 1:59 AM
Added a solution with sample projects I used.
- Open the sln
- Make sure you have x64 selected as platform
- Run "ProcessMemory" without debugging
- Find out its PID (via Process Explorer etc.)
- Go to "ProcessMemoryUsage" properties -> debug and set the PID as sole command line argument
- Run the "ProcessMemoryUsage"

Solution configuration forces the former to run as x64 and the latter to run as x86 and both report the memory usage of the first process. The number reported differs as stated in original post.
Posted by Helen [MSFT] on 10/11/2012 at 9:56 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project to demonstrate this issue so that we can conduct further research?

We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Macy [MSFT] on 10/11/2012 at 11:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)