Einar,
Sorry couldn't locate again. It was something about thread.
Anyway I found what was causing my case:
I had a type that registers an eventhandler. Besides normal instances I had a routine where I create temporary instances (they quickly go out of scope). GC forced collection didn't help BTW (makes sense there are references). Unsubscribing the eventhandler explicitly fixed the issue.
PS: Profiler tool was a time waste for me (trying to uınderstand how it works, so I dismissed. It might be great for someone who understands it but I didn't take my time learning it).
Thanks to all who replied.
Cetin

>In theory pure managed code should not cause memory leaks. Could you please post the links you mentioned if you cn find them. Very interesting stuff.
>
>>Well yes for a second time:) I thought it was already widely known.
>>Cetin
>>
>>>Are you getting memory leaks with managed .Net code?
>>>
>>>>Yes.
>>>>Cetin
>>>>
>>>>>Are you getting memory leaks with .Net code?
>>>>>
>>>>>
>>>>>>Do you know any analyser tool that could detect code that would cause memory leaks?
>>>>>>TIA
>>>>>>Cetin