Chilkat IMAP service is stuck on 100% CPU after several days the Windows service that uses executes normally. It is being reproduced every several days (3-7 days).
I'm using Chilkat IAMP for .NET 4.5 version 9.5.0 64-bit.
From the logs, I get: WSAECONNABORTED An established connection was aborted by the software in your host machine.
The service that runs it resides in a virtual cloud environment.
Is this an issue with how Chilkat IMAP connection is implemented, the cloud environment implementation or something from my service (the application that uses the Chilkat module)...?
The following are Chilkat logs:
asked May 28 '14 at 03:52
If a Chilkat method call never returns and utilizes 100% of the CPU, then you would not be able to get the contents of the LastErrorText. The fact that you have a LastErrorText indicates that the Chilkat method call has returned and your app then proceeded to display the LastErrorText.
My guess is that your app has a loop where normally a Chilkat method call involving communications with an IMAP mail server succeeds (with a normal amount of time spent communicating with the server), but then for some reason the method call begins returning immediately a failed status. At that point, I suspect your application is probably in a tight loop calling the Chilkat method over and over. The 100% CPU utilization is likely caused by the loop in your app, NOT by code within a call to a Chilkat method.
answered May 28 '14 at 11:36