c# - How do I debug an unresponsive .Net Service when "break all" does not respond? -
we have wcf service application consuming large amount of memory (see other ticket today at: server leaking memory; process looks fine).
after extensive use of windows service application @ sudden moment whole service crashes. during moment:
- the log (wcf-trace/server db log) display activity, no leads.
- the memory high, no out of memory exception server leaking memory; process looks fine
- number of open connections; before 'the crash': 10 - 20 memory dump shows 8 threads, without interesting stack trace. these small stacks, without user code (only calls in microsoft-symbols)
can do:
- attach remote debugger;
- connect port wcf listing to;
can't do:
- remote debugger; break not respond
- attach scitechmemoryprofiler (exception:
0x80007002
) - response call of wcf;
the memory still in use, server unresponsive.
thanks reading ticket.
we found solution. analyzed dump file windebug, , found single function in dump. don't know if luck or expected behaviour windows service in .net , there able replicate issue.
thanks reading, , can make progress 'solution'.
Comments
Post a Comment