Back to "Memory Leak - solved - or 'When STAThread Goes Bad'"

This is a viewer only at the moment see the article on how this works.

To update the preview hit Ctrl-Alt-R (or ⌘-Alt-R on Mac) or Enter to refresh. The Save icon lets you save the markdown file to disk

# Memory Leak - solved - or 'When STAThread Goes Bad'

<datetime class="hidden">2003-11-17T00:00</datetime>


## 
[Memory Leak - solved - or 'When STAThread Goes Bad'](https://web.archive.org/web/http://www.mostlylucid.co.uk/archive/2003/11/17/621.aspx)

posted on [11:40 PM](https://web.archive.org/web/http://www.mostlylucid.co.uk/archive/2003/11/17/621.aspx)

I posted a little while ago about an odd 'Memory Leak' I was having...well, after several days of trawling (and annoying [Data Wanta](http://weblogs.asp.net/dwanta/)who's excellent email [component](http://www.aspnetemail.com/) I was mistakenly blaming - sorry!), I finally found the answer! Turns out that the little [STAThread] attribute above the main class of the Comand Line app isn't so inoccuous after all - Dave pointed out [this thread](http://groups.google.com/groups?hl=en&amp;lr=&amp;ie=UTF-8&amp;oe=UTF-8&amp;frame=right&amp;th=d80d655cf0d70930&amp;seekm=ef9gTVwLDHA.1720%40TK2MSFTNGP11.phx.gbl#link1) - apparently there's some sort of [bug in .NET](http://groups.google.com/groups?hl=en&amp;lr=&amp;ie=UTF-8&amp;oe=UTF-8&amp;selm=eXa3ObcPDHA.3192%40tk2msftngp13.phx.gbl)  which can lead to what is effectively a leak when using multi-threading in a STAThreaded application!

This is a preview from the server running through my markdig pipeline

Imported mostlylucidcouk

Memory Leak - solved - or 'When STAThread Goes Bad'

Monday, 17 November 2003

Memory Leak - solved - or 'When STAThread Goes Bad'

posted on 11:40 PM

I posted a little while ago about an odd 'Memory Leak' I was having...well, after several days of trawling (and annoying Data Wantawho's excellent email component I was mistakenly blaming - sorry!), I finally found the answer! Turns out that the little [STAThread] attribute above the main class of the Comand Line app isn't so inoccuous after all - Dave pointed out this thread - apparently there's some sort of bug in .NET which can lead to what is effectively a leak when using multi-threading in a STAThreaded application!