Home Dashboard Directory Help
Search

VCPkgSrv.exe keeps crashing when I open up VS2012 by dkarnadi


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 782073
Opened: 3/25/2013 12:52:28 PM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

I am working in C++ environment using BOOST header files. Initially when i installed VS2012 professional, i did not have any problem with intellisense. But lately, every time i open up my solution, VCPkgSrv.exe keeps crashing on me. After VCPkgSrv.exe crashes, I lose intellisense.
Details
Sign in to post a comment.
Posted by Microsoft on 4/4/2013 at 11:53 PM
Hi dkarnadi, we'll close this feedback since we have not received your response so far. Thanks.
Posted by Microsoft on 4/2/2013 at 3:09 AM
Hi dkarnadi, we want to remind you we have sent new comments to you. Please reply to us as soon as possible. Thanks for your time.
Posted by Microsoft on 3/28/2013 at 3:05 AM
Hi dkarnadi, we want to remind you we need some more information. Please reply to us in time, Thanks a lot.
Posted by Microsoft on 3/26/2013 at 12:01 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting a 32 bits dump file. We look forward to hearing from you with this information.
If the dump file is too large to attach, please upload it into the following workspace.
************************************************************
Please zip the file and use "FeedbackID-782073" as prefix of the file name.
************************************************************
You can use the following workspace to upload the file by IE: https://sftemea.one.microsoft.com/choosetransfer.aspx?key=4714c7a4-1646-49f2-8e2c-91f818cdd165
Password: g#8EJcuGOqrKZ8N
Thanks again for your efforts and we look forward to hearing from you.
Posted by Microsoft on 3/25/2013 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.