3

Closed

nuget crashes when building project

description

This seems to happen each and every time :(

Is there any more details I can provide to help getting this resolved?

3>C:\Work\hg\uxf\2012.10.nuget\NuGet.targets(6,9): error MSB3073: The command ""C:\path\to\project.nuget\nuget.exe" install "C:\path\ŧo\project\packages.config" -source "" -o "C:\path\to\project\packages"" exited with code -1073741819.


Problem signature:
Problem Event Name: APPCRASH
Application Name: NuGet.exe
Application Version: 2.0.30828.5
Application Timestamp: 503cdd85
Fault Module Name: clr.dll
Fault Module Version: 4.0.30319.17929
Fault Module Timestamp: 4ffa5753
Exception Code: c0000005
Exception Offset: 00371a6a
OS Version: 6.1.7600.2.0.0.256.4
Locale ID: 1053
Additional Information 1: 70b8
Additional Information 2: 70b851185f2ba8986f14a6904c238c05
Additional Information 3: 9e49
Additional Information 4: 9e4932d306273eca6b249a1c99e7c8b9

This is with VS 2012 on Win7 x64 i7 hyperthreading enabled

file attachments

Closed Jun 5, 2013 at 9:44 PM by dotnetjunky
Please reopen this bug when you have had a chance to verify with NuGet 2.5

comments

anurse wrote Nov 2, 2012 at 5:12 PM

In order to better debug this issue, we need some process dump files. Windows Error Reporting should prompt you to submit these when you next encounter the issue. If you are familiar with locating and collecting minidumps, please go ahead and do so, but it should be done automatically for you.

Thanks!
Andrew

anurse wrote Nov 7, 2012 at 5:43 PM

I'm bumping this to 2.3, but please do get back to us if you can get a dump or if Windows Error Reporting prompts you to submit additional data.

PedroLamas wrote Nov 14, 2012 at 1:33 PM

I'm actually seeing this too when executing builds in Jenkins!

PedroLamas wrote Nov 14, 2012 at 4:42 PM

Here's a dump file for the error!

I created the dump file with procdump from Sysinternals, adding "procdump -accepteula -x c:\dumps " before the Nuget command like this sample here:

1>C:\J\jobs\test\workspace\Device_Jenkins\Build.targets.LoadNuGetPackages(11,3): error MSB3073: The command "C:\J\jobs\test\workspace\Device.nuget\procdump -accepteula -x c:\dumps nuget install C:\J\jobs\test\workspace\Device\Nokia.AutomationClient\CommandLine\AutomationHost\packages.config -o C:\J\jobs\test\workspace\Device\packages" exited with code 1. [C:\J\jobs\test\workspace\Device_Jenkins\Build.proj]

Without procdump I usually get the -1073741819 error code.

PedroLamas wrote Nov 15, 2012 at 10:01 AM

I created a new dump file with procdump using the "-ma" to get all the process memory.

The file is 8MB and Codeplex doesn't allow me to upload it, so you can find it here:

http://dl.dropbox.com/u/28356/gc/NuGet_121115_105332.dmp

dotnetjunky wrote Jan 22, 2013 at 5:22 PM

Can you try updating your nuget.exe to the latest 2.2 version?

PedroLamas wrote Jan 22, 2013 at 9:20 PM

i'll try it tomorrow, but I must tell you that this issue has appeared a few times in my local machine (Windows 8 x64, VS 2012, nothing special!)

Even on our build server the issue had a random occurrence, so in the end we just applied the old rule of "at first you don't succeed, try and try again": we changed NuGet's MSBuild script to run NuGet a #1 time, if it fails, we will retry a #2 time, and if that one also fails, we will retry a 3rd time and only then we will abort the build process!

The changes to NuGet's MSBuild file did the trick perfectly for us, but this is just hiding the issue... we still see the NuGet failures in the logs!

PedroLamas wrote Feb 13, 2013 at 2:10 PM

Small update over this, I'm still getting the same error sometimes, but here's what we did to bypass the problem:

http://www.pedrolamas.com/2013/02/04/error-nuget-exe-exited-with-code-1073741819/

dotnetjunky wrote Mar 18, 2013 at 11:12 PM

Hi, have you had a chance to try the latest 2.2 build? Or better yet, try our latest nightly build at http://build.nuget.org/Nuget.exe?

dotnetjunky wrote Mar 27, 2013 at 6:04 PM

Load balance to Fei. Please note that this crash dump is collected on nuget.exe 2.1

PedroLamas wrote Mar 28, 2013 at 11:16 PM

Sorry for the delay in replying, but we've been moving our build server to another machine so I hadn't got the chance to check it before...
Next Tuesday I'll go to the build server, deactivate our "fix" and use the latest version as specified and report our findings.