Visual studio 2010 crash and restart on publish to Azure

Question

For some reason visual studio 2010 crashes and restart on publish to the cloud.

This is specific for one big role (about 50mb).

Visual studio dies just before he opens the status in win azure activity log.

In about 10 attempts one works and the role gets uploaded and started.

VS crash even if I just select to create a package in publish dialog.

Error log:

Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.Build.Shared.InternalErrorException
Stack:
   at Microsoft.Build.Shared.ErrorUtilities.ThrowInternalError(System.String, System.Exception, System.Object[])
   at Microsoft.Build.BackEnd.RequestBuilder.RequestThreadProc()
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()

This is the crash report tha VS creates:

Version=1
EventType=CLR20r3
EventTime=129451958347338984
ReportType=1
Consent=1
UploadTime=129451958351858984
ReportIdentifier=066f4938-53d2-11e0-8b91-70f3952d24e2
Response.BucketId=1195077025
Response.BucketTable=5
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=devenv.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=10.0.30319.1
Sig[2].Name=Problem Signature 03
Sig[2].Value=4ba1fab3
Sig[3].Name=Problem Signature 04
Sig[3].Value=mscorlib
Sig[4].Name=Problem Signature 05
Sig[4].Value=4.0.0.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=4ba1da6f
Sig[6].Name=Problem Signature 07
Sig[6].Value=3faf
Sig[7].Name=Problem Signature 08
Sig[7].Value=57
Sig[8].Name=Problem Signature 09
Sig[8].Value=ONVT03M1RZ20JLPUEBOPCNHAKX0UJFRN
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
UI[3]=Microsoft Visual Studio has encountered a problem and needs to close.
UI[4]=If you had files open that contained unsaved changes, these changes might be lost.
UI[5]=Check online for a solution and restart the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
Sec[0].Key=LCID
Sec[0].Value=1033
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=iData=1/nDumpFile=//Upload//iCab//5E07174C052F4BA5B62791F402E0426E.cab/nDumpServer=watson105.watson.microsoft.com/nResponseServer=watson105.watson.microsoft.com/nResponseURL=//dw//GenericFour.asp?iBucket=1195077025&szCab=5E07174C052F4BA5B62791F402E0426E.cab&EventType=CLR20r3&MID=AD4C023B-8267-4315-A162-3B1A5BCAED77/nMemoryDump=1/nBucket=1195077025/nBucketTable=5/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=Microsoft Visual Studio
AppPath=C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe

This drives me crazy, and it is a big waste my time. Please help, I don't know what other info I can post.

Answer 1

Upgraded to .net 4.0 and SDK 1.4, same crash ...

Answer 2

It seems the problem is specific with the application which you mentioned is about 50MB. The application/package size should never be the problem however I think this problem is specific the application specific.

 

First I would try to see if my simple HelloWorld app gives the same problem or not and if yes then it could be tool specific issue means some of the components are not installed properly otherwise application specific.

 

To investigate I would suggest running Process Monitor to log process and file system activities to see when the crash occurred what file/registry was being accessed. If problem happen 90% of the time and build works 10% of the time, you will have the log for both working and non-working case to isolate the files/registry.

 

After that I would check with those files and setting to understand why there is the error. You can use Azure Support team to investigate this issue as well

---

bill boyce

Answer 3

Same behavior with my application ~40MB  and VS2010 or  WebDeveloper Express 2010. 

some workaround?

Answer 4

Have we even similar problems.

For example, VS2010SP1 to crash in the following cases.
1. Web application project, for example, about 20 MByte PDF file contains.
2. This file's Build Action property is Content.
3. This file Copy to Output Directory property is Copy always.

In this State, Publish > Create Service Package Only.
During the cspkg file is not created successfully.
It seems the cspack is being terminated abnormally.

Even if successful, larger file size.

Problem does not occur when you change the file properties.
1. Do not copy this file Copy to Output Directory property.

Sorry bad English.

Answer 5

I am experiencing the same issues here.  Visual Studio crashes when publishing and I have been chasing this for HOURS.  What a pain.  Also, on the few occassions that it has created the publishing files it runs for an hour+ and then fails because the packages are too big.  It seems that publishing doesn't create a consistent size and I get 700MB+ files

Answer 6

I am experiencing the same issue.

Have two or more big zip packages of around 30MB each. Build action = None. Copy always.

The Visual Studio crashes. This was on 32-bit win 7 professional.

 

The same solution file and same package - on win 7 professional 64-bit doesn't crash.

Strange behavior here. Is something to be done on Visual Studio settings for the package size?

 

Thanks

 

Answer 7

+1 on the issue. I've got a pretty big package (> 550 Mb), but crashing is not in the list of required functions for VS I think.

Any updates are very welcome.

Bart

---

Bart Roozendaal, Sevensteps Microsoft MVP for Surface

Answer 8

I believe that this issue is related to another issue with memory.  In our application we are always getting out of memory messages when trying to build the application.  We are using windows 7 - 32 bit with 2 GB RAM.  I just changed the memory to 3 GB and the publish worked...could be a coincidence.  I will have to see after publishing it later.

Answer 9

reproduced with this scenario:

application with ~40MB

win7 32bit with 2 GB Ram crash

win7 64bit with 4 GB Ram works!!!

Answer 10

I was seeing the same issue when the active solution build configuration was mismatched with the Azure packaging build configuration.  Setting both of these to same configuration (Debug or Release) reliably solved the problem.

Answer 11

I came up against this as well. I have a couple pieces of information:

1.I talked to Microsoft Azure support and they said its a known bug and will be fixed in the next version (I'm using azure tools 1.6). They also said you could work around it by building the package and deploying outside of Visual Studio, although I have not tried this.

2. I have been able to get my site to deploy reliably without crashing if I go into my azure project folder every time before I deploy and delete the subfolders bin,csx, and obj.

Answer 12

Hi, 

I solved the issue by following steps

1. I Made sure that Package is not more, it would not build if it also. 
2. Exclude the files which are in large in size. Eg GhostScript which is around ~30MB
3. But u can download them on the startup script just like the java downloaded in this following examples link
4. Trying moving the css, images, js to blob it is another approach. 

Regards

Madan

dmadan.wordpress.com