Search

devenv.exe hangs when simultaneously building same sources by RichChom

Closed
as External Help for as External

1
0
Sign in
to vote
Type: Bug
ID: 775829
Opened: 1/4/2013 11:32:52 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
Simultaneous builds of the same source trees (via ant's parallel task) will often result in an instance of devenv.exe hanging/spinning (consuming ~24% CPU).

The entire build consists of many C++ projects. More often than not, the build of the first project is the one that hangs.
Details (expand)

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

Visual Studio 2012

Steps to reproduce

Build multiple platforms (win32 and x64) of the same solution(s) at the same time (easily done via ant's parallel task).


Attached are two mini-dumps of when devenv.exe hung.

Product Language

English

Operating System

Windows 7 SP1

Operating System Language

English

Actual results

The ant task never completes due to a hung/spinning instance of devenv.exe

Expected results

All builds execute and complete successfully.
File Attachments
File Name Submitted By Submitted On File Size  
Feedback-Id775829.zip (restricted) 1/4/2013 -
Sign in to post a comment.
Posted by Microsoft on 2/20/2013 at 6:14 PM
Hello, and thank you for the feedback. Parallel builds of the same source using custom tasks such as Ant’s Parallel task is not a scenario supported by MSBuild. Apache Ant's Parallel Task documentation (http://ant.apache.org/manual/Tasks/parallel.html) specifically warns against that sort of usage as it must be explicitly supported by the tasks to be run in parallel.
Posted by Microsoft on 1/6/2013 at 11:06 PM
Thanks for your feedback.

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 Microsoft on 1/4/2013 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)
Sign in to post a workaround.