Exceptions from ImapClient.GetMessages() about s22.imap HOT 7 CLOSED

Thanks for reporting. I mainly use Gmail for testing and I haven't experienced this behaviour before. I'll look into it and see if I can figure anything out.

from s22.imap.

Do you still experience this? I can't seem to reproduce this on my end...Have you tried checking out the latest version of the library?

from s22.imap.

I do. I replied to your gmail account with some debugging info.

from s22.imap.

Ah sorry, I misread your original post, those debug messages can be safely ignored, IMO.

From my understanding, a first chance exception is harmless...in some scenarios, you expect some exceptions to happen (like in ParsePriority and some other methods) and the debugger reports those as first-chance exceptions.

Check out this MSDN article about first and second chance exception handling:
http://support.microsoft.com/kb/105675/en-us

from s22.imap.

Thanks for the MSDN link!

From: smiley22 [email protected]
To: smiley22/S22.Imap [email protected]
Cc: bmt22033 [email protected]
Sent: Saturday, February 2, 2013 9:58 AM
Subject: Re: [S22.Imap] Exceptions from ImapClient.GetMessages() (#27)

Ah sorry, I misread your original post, those debug messages can be safely ignored, IMO.
From my understanding, a first chance exception is harmless...in some scenarios, you expect some exceptions to happen (like in ParsePriority and some other methods) and the debugger reports those as first-chance exceptions.
Check out this MSDN article about first and second chance exception handling:
http://support.microsoft.com/kb/105675/en-us
—
Reply to this email directly or view it on GitHub.

from s22.imap.

Regarding this I'm starting to see performance issues that might be because of these first chance exceptions.
Assumption partly based on:
http://msdn.microsoft.com/en-us/library/vstudio/ms229009%28v=vs.80%29.aspx

Added null checks to avoid most of these, found them using: http://blogs.msdn.com/b/davidklinems/archive/2005/07/18/440150.aspx

from s22.imap.

Did you ever implement these null checks in s22?

I'm seeing a lot of them while parsing old emails and although the mail is read correctly, it's causing enough cpu overhead that it's showing up in my performance stats...

from s22.imap.