Hi there,
Just a quick hint here - watch for AppDomain unhandled exceptions. It might
be worth adding some of your debug/trace statements to the AppDomain
Unhandled Exception event.
An unhandled exception in a background thread can sometimes crash or hang an
app.
Good luck,
Geoff
-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Peter Osucha
Sent: 21 February 2008 17:04
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: [ADVANCED-DOTNET] Multiple Threads and app lockup
Hello.
I'm hoping someone might provide me some direction on troubleshooting an
app. It's one of the first apps I have been involved with that makes
use of multiple threads. The app also connects to another computer by
way of an AsynchTCP socket. Also, the app is on a single board computer
embedded system (running WinXP Embedded) - end result, there is not
enough room on the target system to install VS2005 so I can't run from
the IDE to see what is happening.
Anyway, I often find this app to be in a non-responsive state and I have
to kill it with the task manager. I've put in some debug/trace
statements but either I'm not putting in enough of them or they are in
the wrong place - end result, I'm don't seem to be getting any closer to
figuring out why the app keeps getting to a non-responsive state. It
does seem that the app becomes non-responsive with greater frequency if
I have opened up the TCP connection than if I haven't - leading me to
believe that might be involved with the problem condition. But again,
my debug/trace statements aren't getting me closer to solving the
problem.
Comments?
Sincerely,
peter
===================================
This list is hosted by DevelopMentor. http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
