ASPRUNTIME: The application domain in which the thread was running has been unloaded.

Question

We're running Jekins which kicks off a gulp build process. As part of the gulp build process we trigger an msbuild task.

Every second build fails with the message:

ASPNETCOMPILER : error ASPRUNTIME: The application domain in which the thread was running has been unloaded.

This happens exactly every other build no matter the time span between builds. (i.e. Builds, Fails, Builds, Fails).

Any ideas on what might be causing this and why it happens only every other build?

score 11 · Answer 1 · edited May 23 '17 at 11:45

11

I also had this problem on a machine with enough memory. Turns out the problem was due to the target folder being Compressed using NTFS compression.

Once compression was disabled it started working without problems.

I saw that this could be a problem here.

edited May 23 '17 at 11:45

Community

1
1

answered Aug 08 '16 at 14:46

Pablo Montilla

2,941
1
31
35

1

Had the same problem. (Jenkins and via `cmd.exe`.) Interestingly it worked if I called `aspnet_compiler.exe` (via `cmd.exe`) directly the same way as MSBuild does. But if run via MSBuild it failed. Otherwise not. Go figure! Somehow related: Never ever compress stuff where MS SQL Server stores it's database files. – Sleepless Annoyed Nerd Aug 24 '16 at 15:14

score 5 · Accepted Answer · answered May 14 '15 at 17:35

5

We solved this problem by allocating more memory to the build machine.

answered May 14 '15 at 17:35

Jamie Dixon

53,019
19
125
162

Thanks to this answer i tried to close unnecessary applications and it fixed the problem. – Omtechguy Dec 24 '18 at 15:17

score 1 · Answer 3 · answered Aug 30 '17 at 11:29

1

A little late to the party but for googlers: I had a similar problem when doing a build in visual studio. Turns out Dropbox was locking the compiled dlls. Once I'd excluded the bin directories (did obj directories too for good measure) the problem went away. This may also be the case for antivirus/antimalware programs too.

answered Aug 30 '17 at 11:29

Mark Ball

366
2
10

This is still a problem; literally just ran into this same thing via VS2019 (on 2020.11.22). – azarc3 Nov 22 '20 at 19:15

score 0 · Answer 4 · answered Aug 05 '21 at 03:20

0

The same error in my case was fixed by disabling memory compression.

I ran in elevated power shell

Disable-MMAgent -mc

and reboot

(Can be re enabled by Enable-MMAgent -mc)

answered Aug 05 '21 at 03:20

profaisal

57
5

ASPRUNTIME: The application domain in which the thread was running has been unloaded.

4 Answers4