Please stop guessing, start measuring. There are a number of good memory
profilers around for .NET.
First there is the 'ClrProfiler' freely downloadable from
http://www.microsoft.com/downloads/...1C-3870-43BE-8926-862B40AA0CD0&displaylang=en
another decent one is the scitech profiler, a preview is available from
http://www.scitech.se/.
Willy.
| Wiktor:
|
|
|
| Yes the memory consumption increases constantly by small fractions and
then
| the
| crash is happening. Basically my module is processing lot of events. Crash
| is depending on no of events it is processing. Those events are trigged by
| external another managed code module.
|
|
|
| For example:- Agent Signed In event.
|
| If no. of agents signed in is high, it will crash immediately.
|
|
|
| Thanks,
|
| Raja.GS
|
|
|
| message | > > Chances are you're holding on to a reference somewhere that you
| > > shouldn't be. Without seeing any code or having any other information,
| > > it's impossible to say more than that, really.
| > >
| > > Jon
| > >
| >
| > Jon - while developing several big applications (managed-code only!) I
| have
| > seen very rare and nondeterministic [Out of memory] exceptions. I belive
| > then that the garbage collector could somehow be mistaken in those few
| > situations (does anyone have a formal proof of gc correctness? I do not
| > think so and even if the proof exists it only proves that the algorithm
is
| > correct and not the actual implementation). However, since I've never
been
| > able to reproduce these problems, I've never paid much attention to
them.
| >
| > Raja - do you monitor the memory consumption of your application? Does
the
| > memory consumption increases constantly by small fractions and then the
| > crash happens? Or maybe the memory stays at some fixed rate but then
there
| > is a sudden allocation of big block of memory that causes the crash?
Also,
| > as Simon suggested, are you using unmanaged resources?
| >
| > Wiktor Zychla
| >
|
|