Question:
I'm having a problem with Chilkat .Net 4 x64 ( Version 9.4.0.0 ). From time to time our service crashes with a AccessViolationException at searching in a imap inbox for new mails. May the pre release version 9.4.1.0 resolve this Problem?
Chilkat.MessageSet messageSet = null;
bool fetchUids;
fetchUids = true;
string notSeenSearch;
notSeenSearch = "NOT SEEN";
messageSet = imap.Search(notSeenSearch, fetchUids);
Chilkat.EmailBundle bundle = null;
bundle = imap.FetchBundle(messageSet);
The Exception:
Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException Stack: at <module>.ClsImap.FetchBundle(ClsImap, ClsMessageSet, ProgressEvent) at <module>.ClsImap.FetchBundle(ClsImap, ClsMessageSet, ProgressEvent) at Chilkat.Imap.FetchBundle(Chilkat.MessageSet) at LiberoManager.Service.MailService.CheckMail(LiberoManager.Data.Customer, Int32, System.String, System.String) at LiberoManager.Service.MailService.Run(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.TimerQueueTimer.CallCallback() at System.Threading.TimerQueueTimer.Fire() at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch()
Yes, this new version should solve it:
.NET 4.0 x64 assembly: http://www.chilkatsoft.com/preRelease/ChilkatDotNet4-9.4.1-x64.zip
I am having the same issue as described above. I originally received the error on version 9.4.1. To be thorough, I just upgraded to the latest version of 9.5.0.48 of the 64 bit .net 4.0 dll and I'm still receiving the error. It does not occur consistently. Any help would be appreciated.
Here is the unhandled exception that is thrown:
Application: WaWorkerHost.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException Stack: at <module>.ClsImap.FetchBundle(ClsImap, ClsMessageSet, ProgressEvent) at <module>.ClsImap.FetchBundle(ClsImap, ClsMessageSet, ProgressEvent) at Chilkat.Imap.FetchBundle(Chilkat.MessageSet) at EmailServiceProcessor.EmailServiceClass.RetrieveEmails(Boolean) at EmailRetrieval.ProcessQueueItemsJob.ProcessRetrievalForAccount(System.String ByRef, EmailServiceProcessor.EmailServiceClass ByRef) at EmailRetrieval.ProcessQueueItemsJob.ProcessRetrievalQueueItem() at EmailRetrieval.ProcessQueueItemsJob.Execute(Quartz.IJobExecutionContext) at Quartz.Core.JobRunShell.Run() at Quartz.Simpl.SimpleThreadPool+WorkerThread.Run() at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart()
Please test with this new v9.5.0.49 pre-release:
32-bit Download: http://www.chilkatsoft.com/download/preRelease/ChilkatDotNet4-9.5.0-win32.zip
64-bit Download: http://www.chilkatsoft.com/download/preRelease/ChilkatDotNet4-9.5.0-x64.zip
I suspect an out-of-memory issue caused a crash. Chilkat has done extensive work since v9.5.0.48 to help ensure that out-of-memory conditions don't cause access violations. This may solve the problem.
Thank you for the updated dll.
So far the issue seems to be resolved.