Search

Microsoft (R) Visual C++ Package Server Hangs (100% CPU usage) by Darcy Harrison

Active

1
0
Sign in
 to vote
Type: Bug
ID: 771430
Opened: 11/16/2012 1:11:25 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
In our medium sized Windows Store App, on all our machines, Visual Studio 2012 hangs and uses 100% of one CPU while it appears to be calculating something related to Intellisense.

The editor is still able to be used normally, except "Go To Definition/Declaration..." will hang the editor window until the runaway package server is manually terminated. A new instance will immediately spin up and use 100% of one cpu.

With CPS "verbose" logging enabled, I see this:

[5092] Error -
[5092] Invalid args, too big block
[5092]
[5092] Error -
[5092] Invalid args, too big block
[5092]
[5092] Error -
[5092] Invalid args, too big block
[5092]
[5092] Error -
[5092] Invalid args, too big block
[5092]

Every time the package server goes nuts.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

I'm not sure how to exactly reproduce it. It seems to happen with most but not all of the source files in the project. Just having one of them open in a tab will set it off once Intellisense decides to update.

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

Microsoft (R) Visual C++ Package Server runs at 100% CPU utilization forever. Some Intellisense operations block the main GUI until the server is manually killed. Intellisense stops working on some source files.

Expected results

Intellisense would not hang. Happiness and joy would be prevalent throughout the land.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Darcy Harrison on 4/8/2013 at 9:55 AM
Hi Karl,

I am trying to upload a new .dmp file, but it appears that the workspace: https://sftus.one.microsoft.com/choosetransfer.aspx?key=9415c965-6590-4d5f-8331-614ff9c106df is now invalid. Can you please provide an alternative location for me to upload the files? Also do you want a dump of devenv in addition to vcpkgsrv?

~Darcy
Posted by Microsoft on 4/3/2013 at 10:55 PM
Hi Darcy,

We can't seem to reproduce this bug. You mentioned on 11/20/2012 that a 32 bit dump has been uploaded, but it does not appear in the set of attachments. Can you perhaps upload it again? Thanks.

Karl Niu
VC++ Team
Posted by Microsoft on 3/18/2013 at 6:19 PM
Hi Darcy,

Thank you for providing this information; our devs are now aware of the problem. Unfortunately, though this issue is indeed quite severe, we shall focus on fixing other bugs for our next release. This bug has been copied to our backlog and will be addressed in a future release.

Thanks,
Karl Niu
Visual C++ Compiler Team
Posted by Darcy Harrison on 11/28/2012 at 9:39 AM
Just FYI, Update 1 did not address this problem.
Posted by Microsoft on 11/21/2012 at 2:08 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Darcy Harrison on 11/20/2012 at 9:18 AM
32 Bit dump is now uploaded.
Posted by Microsoft on 11/20/2012 at 1:54 AM
Could you please collect dumps of 32-bit process? We should use 32-bit version of Debugger like Debug diag x86 to collect manual dumps for 32-bit process on 64-bit server. Using 64-bit Debugger or task manager will create a 64-bit dump. This will have dump of the syswow64 and it won't allow extensions like psscor, sos to read it properly in windbg and addresses are 64 bit addresses [even though process is 32-bit].
Windows Server 2008 and Windows 7 have a built-in 32-bit task manager under C:\Windows\SysWOW64\taskmgr.exe. We can use this and select "Create Dump File" for 32-bit process. To confirm we are using 32-bit task manager, check the process name of it. It should be taskmgr.exe *32
Please upload a 32bit devenv's dump. Thanks for your time.

http://blogs.technet.com/b/sateesh-arveti/archive/2011/07/10/easier-way-to-collect-dumps-of-32-bit-process-on-64-bit-server.aspx
Posted by Darcy Harrison on 11/19/2012 at 9:37 AM
Done.
Posted by Microsoft on 11/18/2012 at 11:25 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting a dmp file. Please submit this information to us within 4 business days. We look forward to hearing from you with this information.
************************************************************
Please zip the file and use "FeedbackID-XXXXXX" as prefix of the file name.
************************************************************
You can use the following workspace to upload the file by IE: https://sftus.one.microsoft.com/choosetransfer.aspx?key=9415c965-6590-4d5f-8331-614ff9c106df
Password: Z1_)G37MTk
Thanks again for your efforts and we look forward to hearing from you.
Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 11/16/2012 at 1:51 PM
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)
Sign in to post a workaround.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement