Home Dashboard Directory Help
Search

Inconsistent Hanging with DEVENV 2010 by GSB


Status: 

Closed
 as Fixed Help for as Fixed


13
0
Sign in
to vote
Type: Bug
ID: 595632
Opened: 9/6/2010 11:00:28 PM
Access Restriction: Public
1
Workaround(s)
view
12
User(s) can reproduce this bug

Description

We have setup a new Windows 7 32 Bit Virtual Machine under HyperV R2, and we are getting periodic hangs of Devenv.exe in our build process.

We must use devenv.exe to build our .vdproj setup projects (within solutions of C# 2.0 projects).

The build process simply hangs during the build of some (not always the same one) of our projects, and the process running at that point is Devenv.exe.
Details
Sign in to post a comment.
Posted by Jenska on 3/21/2013 at 7:48 AM
We're seeing this behavior on VMWare W2k8 sp2 VM's with VS 2010 SP1. Ours seems to be the reverse case however, in that it only seems to occur on single-cpu machines, and not on dual-cpu systems. There was once a race (VS 6.0) in the startup where multiple threads were used to provide initialization the projects. While they always finished before the GUI user could start a build, this was not true for automated builds, but that caused the build to fail, not hang.
Posted by Scott Bakker on 3/15/2013 at 11:03 AM
This started the day we moved our source servers to Virtual Servers (I don't know the brand), and never happened before. We get it using VS 2012 compiling all types of VB.NET projects. It is using a batch file to run the "devenv" compiles, and outputs to a log file, all on those Virtual Servers. The log file is locked for about 60 seconds after the batch file hangs, then it is released. Re-running the batch file will allow one or several more projects to compile, but only because the previous projects are "up-to-date", so it isn't trying to build them. Hope this helps! It is an ongoing problem for us.
Posted by coghlans on 3/5/2013 at 6:50 AM
Seen in 2 types of virtual environment (Hyper V on 2k8 & VirtualBox 4.2.x on Win 7x64)
Tried reducing number of cores down from 7 to 3
Tried installing hotfix KB2444922.
Does not always hang on some solution
Hangs on Silverlight / C++ / MFC / C# solutions.
All driven via Batch files.

Note:
Seems to be okay, if only a single core is used (But that negates the parallel build engines !)
Posted by k88alb on 4/12/2012 at 1:10 PM
Also seeing same issue.

4 processor machine, 4 msbuilds running with 14, 13, 13, 13, threads respectively.
Running performance monitor shows activity for a period, then it all falls off a cliff.
Can't rely on building to succeed. Occurs both in 32-bit and 64-bit. Seems like a lock issue.
Posted by Jax1157 on 3/15/2012 at 5:52 PM
Hi,

Can confirm that we are also getting this issue - Occurs approx 30% of the time when building (only from command line). System is Windows 7 64 bit.
Posted by Mark at L3 on 3/14/2012 at 9:36 PM
Hi,

We are having the same problem also. We have Visual Studio 2010 with SP1 on a Windows 7 box which does our nightly builds. We build from a script calling devenv.exe. devenv hangs randomly in about 20% of the time we build. We applied the hotfix and it has not improved and devenv still hangs. We are building a large solution around 30 projects. This hanging is most annoying as we can't rely on our build process to work at any given time.

Regards,
Mark
Posted by gjestela on 8/29/2011 at 5:36 AM
We are seeing the same issue. Installing hotfix KB2444922 did not help.
Posted by Microsoft on 8/22/2011 at 12:32 PM
Hi,

We have not heard back from you. We will go ahead and close this issue. If you have other questions, please open a new bug.

Thank you.
Posted by Microsoft on 8/15/2011 at 6:28 PM
Hi,

There seems to be a race condition in the code that is not fixed by the published hotfix. Glad to hear you were able to workaround the issue by rebuilding. Is there anything else that we can help answer before closing this issue?

Thank you.
Posted by Mike J. Wilson on 4/4/2011 at 11:10 AM
This is still an issue with us. The HRESULT = '8000000A' errors occur every so often. Re-running the build will correct it, if we are lucky.
Posted by GSB on 3/8/2011 at 2:16 PM
We have found that retrying the same build after waiting 5-10 seconds succeeds. Not ideal, but a workaround nonetheless.
Posted by ysheldon on 3/8/2011 at 10:10 AM
Hi,

I have the same problem after applying the hotfix as well.

------ Starting pre-build validation for project 'EnqLouthSimInstall' ------
ERROR: An error occurred while validating. HRESULT = '8000000A'
------ Pre-build validation for project 'EnqLouthSimInstall' completed ------
------ Build started: Project: EnqLouthSimInstall, Configuration: Release ------
========== Build: 5 succeeded or up-to-date, 1 failed, 0 skipped ==========

I tried replacing the vdproj with one constructed in VS2010 no luck!

Posted by GSB on 1/19/2011 at 4:25 PM
Hi,

I have noticed some errors in our build logs after applying the hotfix - see below.

------ Starting pre-build validation for project 'Liberty.Admin.Host.Setup' ------
ERROR: An error occurred while validating. HRESULT = '8000000A'
------ Pre-build validation for project 'Liberty.Admin.Host.Setup' completed ------
------ Build started: Project: Liberty.Admin.Host.Setup, Configuration: Release ------
========== Build: 3 succeeded or up-to-date, 1 failed, 0 skipped ==========

Can you please advise what we need to do to avoid this issue ?

Thanks,
Greg
Posted by Microsoft on 1/11/2011 at 12:49 PM
Thank you for the confirmation. We'll consider this issue as closed.
Posted by brownseane on 1/10/2011 at 8:54 PM
Hi,

Applied the Hotfix on the 4-Jan-2011 and have not had Devenv.exe hang since.

Thanks.
Posted by brownseane on 1/4/2011 at 2:55 PM
Hi,

I will try this hotfix today and over the next few days and let you know the outcome.

Thanks.
Posted by Microsoft on 1/4/2011 at 1:55 PM
Hi,

The hotfix is now uploaded on here: http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=33186

We will keep this bug active for another 7 days in case if you have any further issues or questions.

Thank you.
Posted by Microsoft on 12/7/2010 at 12:18 PM
Hi,

Just want to let you know that a hotfix is underway. It will be ready for download within the next few weeks. Stay tuned.

Thank you.
Posted by Microsoft on 11/2/2010 at 11:43 AM
Hi,

Apologize for the delayed response. We are able to reproduce this issue and are looking into producing a hotfix. Stay tuned for further updates.

Thank you.
Posted by Jon Erlend Mathisen on 10/22/2010 at 3:47 AM
Yo partyppl!

I'm also having inconsistent hanging with devenv 2010 when building .vdproj setup projects. What seems to have solved the issue (in my case) is to manually edit the 'Lauch Contitions' (Right click setup project -> View -> Launch Condition'). When I write '2.0.50727' manually into the '.NET Framework Launch Condition Properties', the build seems to be stable. '2.0.50727' is what was used in VS2008 before upgrade of the setup project.

I'm not 100% sure this is a valid solution/workaround, but I just wanted to share my observation.

// JonBaron
Posted by GSB on 10/12/2010 at 3:16 PM
Hi,

Just following up to find out the rough timeframe for this bug to be fixed ?

Thanks,
Greg
Posted by GSB on 10/4/2010 at 7:10 AM
Hi,

This is definitely a blocking issue for us, and it is a significant investment to move away from VDPROJ to ISLE, which we have not considered at this time.

What sort of timeframe are we looking at to have this bug resolved ?

Thanks,
Greg
Posted by Microsoft on 9/27/2010 at 2:53 PM
Hi,

We have identified the problem in the setup project code that causes this issue. Unfortunately, there is no workaround.

Given that we are retiring setup projects in the next release of Visual Studio, we encourage you to consider moving your project to the InstallShield Limited Edition (ISLE) which you can obtain for free of charge with Visual Studio 2010. In addition, there is an import tool in ISLE that allows you to convert a .vdproj to an InstallShield project.

Please let us know if this is a blocking bug for you and whether moving to ISLE is an option you would consider.

Thank you.
Posted by GSB on 9/23/2010 at 7:25 PM
Hi Dan,

If it is the deployment project, that makes sense, as only our MSI builds are hanging.
If you could please let me know ASAP what is causing the hang, I'd appreciate the rapid feedback, as it is impacting the release of our next application version.

Thanks,
Greg
Posted by Microsoft on 9/23/2010 at 3:27 PM
Scratch that, my mistake. The dump file is useful -- I've routed to the correct team.
Meantime, it's cause by a Deployment project doing the "validation" step. I'm not familiar with Deployment projects, but if there's a way to avoid it doing that, it should avoid the hang, or possibly you can keep that project unloaded except when you're building an MSI.
Dan
Posted by Microsoft on 9/23/2010 at 3:11 PM
Hey Greg, the dump file you uploaded won't open for me -- it says it's corrupt. Would you mind uploading another dump file?
You could try procdump.exe from sysinternals.com. It has always given me good dump files.

Dan
Posted by brownseane on 9/22/2010 at 7:05 PM
I'm have this same issue, is there an update / fix to this bug?
Posted by GSB on 9/20/2010 at 3:34 PM
Hi,

Just checking in to see if you have been able to identify anything from the trace I uploaded ?

Thanks,
Greg
Posted by GSB on 9/16/2010 at 12:53 AM
Hi,

I have uploaded the ETL file to the workspace you have identified.

Regards
Greg
Posted by Microsoft on 9/15/2010 at 1:09 AM
Hi GSB,

Could you please collect ETL traces during occurrence of the issue? Please download the VS performance tool from:
http://visualstudiogallery.msdn.microsoft.com/en-us/e8649e35-26b1-4e73-b427-c2886a0705f4
Please read the “Performance Diagnostics Tool – User Guide” document (a shortcut to it should appear on your desktop after install) on steps to generate a trace. Please note that when you uninstall the tool, the settings.ini file will not be removed as it contains your user settings. Also, unfortunately this tool does not work on XP.

Once you have the trace, please upload the file to the following workspace:
https://sftus.one.microsoft.com/choosetransfer.aspx?key=01bf3a0b-0eec-4356-9343-a9ee0c8f30d0
Password:zT)h33NV11@0

Please select "Send Files to Microsoft - Standard" if your trace is less than 2G, else select "Send Files to Microsoft - Resume" to upload the file.

Thanks!

Posted by GSB on 9/13/2010 at 12:49 AM
Do you have a Beta program for VS.NET 2010 SP1 that I might be able to take part in to see if that resolves my issue ?
Posted by GSB on 9/13/2010 at 12:48 AM
We have experienced the same issue when running our build script from Visual Build Professional, but only under VS.NET 2010, however the behaviour was slightly different - the devenv.exe process would appear orphaned in Process Explorer, not under the process that started it.
Posted by Microsoft on 9/12/2010 at 11:43 PM
Could you please run devenv.exe directly rather than through Jetbrains TeamCity and see if the problem reproduces?

Posted by Microsoft on 9/7/2010 at 6:41 PM
Thank you for reporting the issue.
We are routing 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 9/7/2010 at 2:37 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.
Posted by coghlans on 3/21/2013 at 5:36 AM
I have found a workaround that works 95% of the time, and then finally managed to nail it explicitly for our problem

1) I added a delay after each complete solution build (i.e. after the devenv command line call) that was incremented until the builds passed 95% of the time (whereas before they would fail 50%)
This is done by simply calling
ping 127.0.0.1 -n %1 > nul
And pass in a value of seconds
We started at 5 and depending on the speed of the machine went upto 12.

2) Our instance:
We found that the build machines that were failing the most had had an update to a devEnv plugin from a big company called (HAL ---) [Take away a letter in the alphabet]
Uninstalling this plugin, made the devenv work all the time.
The next step was to remove all the plugins on the Build machines.
So now we have placed /SafeMode on the devenv command line and removed the delay, and this has prooved to be successful, and sped the builds again, as I can now use all the available core in HyperV and VirtualBox :-)
File Name Submitted By Submitted On File Size  
devenv_Liberty.DocumentManagement.log (restricted) 9/6/2010 -
devenv_dump.zip (restricted) 9/6/2010 -