Databases
StackOverflow2013
Postsdbo
POHow can I prevent CompileAssemblyFromSource from leaking memory?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow can I prevent CompileAssemblyFromSource from leaking memory?
    primarykey
    data
    text
    <p>I have some C# code which is using CSharpCodeProvider.CompileAssemblyFromSource to create an assembly in memory. After the assembly has been garbage collected, my application uses more memory than it did before creating the assembly. My code is in a ASP.NET web app, but I've duplicated this problem in a WinForm. I'm using System.GC.GetTotalMemory(true) and Red Gate ANTS Memory Profiler to measure the growth (about 600 bytes with the sample code).</p> <p>From the searching I've done, it sounds like the leak comes from the creation of new types, not really from any objects that I'm holding references to. Some of the web pages I've found have mentioned something about AppDomain, but I don't understand. Can someone explain what's going on here and how to fix it?</p> <p>Here's some sample code for leaking:</p> <pre><code>private void leak() { CSharpCodeProvider codeProvider = new CSharpCodeProvider(); CompilerParameters parameters = new CompilerParameters(); parameters.GenerateInMemory = true; parameters.GenerateExecutable = false; parameters.ReferencedAssemblies.Add("system.dll"); string sourceCode = "using System;\r\n"; sourceCode += "public class HelloWord {\r\n"; sourceCode += " public HelloWord() {\r\n"; sourceCode += " Console.WriteLine(\"hello world\");\r\n"; sourceCode += " }\r\n"; sourceCode += "}\r\n"; CompilerResults results = codeProvider.CompileAssemblyFromSource(parameters, sourceCode); Assembly assembly = null; if (!results.Errors.HasErrors) { assembly = results.CompiledAssembly; } } </code></pre> <p><strong>Update 1:</strong> This question may be related: <a href="https://stackoverflow.com/questions/1162686/dynamically-loading-and-unloading-a-a-dll-generated-using-csharpcodeprovider">Dynamically loading and unloading a a dll generated using CSharpCodeProvider </a></p> <p><strong>Update 2:</strong> Trying to understand application domains more, I found this: <a href="http://codebetter.com/blogs/raymond.lewallen/archive/2005/04/03/61190.aspx" rel="nofollow noreferrer">What is an application domain - an explanation for .Net beginners</a></p> <p><strong>Update 3:</strong> To clarify, I'm looking for a solution that provides the same functionality as the code above (compiling and providing access to generated code) without leaking memory. It looks like the solution will involve creating a new AppDomain and marshaling.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USNogwater
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow can I prevent CompileAssemblyFromSource from leaking memory?
      1. USDan Byström
      1. VTFavorite
    2. VO
      singulars
      1. POHow can I prevent CompileAssemblyFromSource from leaking memory?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow can I prevent CompileAssemblyFromSource from leaking memory?
      1. USNogwater
      1. VTBountyStart
    1. COVery cool question. I'll have an example of how to do this using another AppDomain by the end of today (I'm currently eating lunch, then back to work...).
      singulars
      1. POHow can I prevent CompileAssemblyFromSource from leaking memory?
      1. USCharles
    2. COWhat are you planning to do with the resultant assembly? Is it just for a one time execution or are you going to hold on it?
      singulars
      1. POHow can I prevent CompileAssemblyFromSource from leaking memory?
      1. USmadaboutcode
    3. CO@LightX I'm going to hold on to it for a while and invoke members from it as needed, but then when a new version of the source code is available, I'll want to dump it and create a new assembly based on the new code. Without the AppDomain fix, this cycle of repeatedly creating assemblies (even though I stop referencing the old versions) causes memory usage to grow.
      singulars
      1. POHow can I prevent CompileAssemblyFromSource from leaking memory?
      1. USNogwater
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload