LoaderLock was detected

Blimey … what was that? This kind of exception, that only happens during debugging, confuses developers. Googling about the problem shows that Microsoft at times gives pointless answer. Some blame iTunes about this problem ;)

Rather than following the advice to turn this rather useful check in VS 2005, the most probable causes of this problem are:

1) An unmanaged dll calls a managed dll on its DLLMain or
2) Not marshalling your call back to the main UI thread.

Vivek wrote a bit more about this problem here.