D
Dennis
I am trying to debug a service that I wrote that uses a
System.Threading.Timer to periodically fire off a handler that opens a
socket to a pop3 server and retrieves emails.
It works OK most of the time, but every so often I notice that one of
the dual cpu's pegs at 100% usage.
I used Process Explorer to look at the service and I am seeing that one
of the TCP/IP connections is stuck in CLOSE_WAIT. I don't know if this
is what is causing the cpu to peg, because Process Explorer eventually
shows that the CLOSE_WAIT connection disappears ... but the cpu stays
pegged at 100% until I stop the service.
I have attached the debugger and no exceptions appear to be thrown.
The CLOSE_WAIT business doesn't bother me so much. It is the cpu usage
that I am concerned about.
The cpu is pegged at 100% as I type. Any suggestions as to what I can
look at to track this behavior down?
System.Threading.Timer to periodically fire off a handler that opens a
socket to a pop3 server and retrieves emails.
It works OK most of the time, but every so often I notice that one of
the dual cpu's pegs at 100% usage.
I used Process Explorer to look at the service and I am seeing that one
of the TCP/IP connections is stuck in CLOSE_WAIT. I don't know if this
is what is causing the cpu to peg, because Process Explorer eventually
shows that the CLOSE_WAIT connection disappears ... but the cpu stays
pegged at 100% until I stop the service.
I have attached the debugger and no exceptions appear to be thrown.
The CLOSE_WAIT business doesn't bother me so much. It is the cpu usage
that I am concerned about.
The cpu is pegged at 100% as I type. Any suggestions as to what I can
look at to track this behavior down?