Notifications Stopping

Naresh, you are literally the only person that has reported this behaviour. Do you have another PC you can try it on and see if it is the same on that?

I suspect this is the same problem I was seeing. I haven't been able to use OWATray since the changes to the growl message format. Here's the message again:

After running this successfully for a while, I saw that the latest
build (v1.0.3601.16774 ) of OWAtray was taking up 100% CPU and is
unresponsive. Dont know what triggered this state. Doesn't seem to be
throwing managed exceptions or chewing memory, so it's probably just
stuck in a tight loop somewhere. The stack trace of the thread in
question doesn't seem too helpful:

ntkrnlpa.exe!NtBuildNumber+0x43
ntkrnlpa.exe!MmIsDriverVerifying+0xbb0
hal.dll!HalClearSoftwareInterrupt+0x342
System.Windows.Forms.ni.dll+0x1f849a
USER32.dll!GetDC+0x6d
USER32.dll!GetDC+0x14f
USER32.dll!GetWindowLongW+0x127
USER32.dll!DispatchMessageW+0xf
System.Windows.Forms.ni.dll+0x208cce
System.Windows.Forms.ni.dll+0x208937
System.Windows.Forms.ni.dll+0x208781
System.Windows.Forms.ni.dll+0x1c5911
mscorwks.dll+0x1b4c
mscorwks.dll!DllUnregisterServerInternal+0x6195
mscorwks.dll!CoUninitializeEE+0x2e95
mscorwks.dll!CoUninitializeEE+0x2ec8
mscorwks.dll!CoUninitializeEE+0x2ee6
mscorwks.dll!GetPrivateContextsPerfCounters+0xf546
mscorwks.dll!GetPrivateContextsPerfCounters+0xf466
mscorwks.dll!GetPrivateContextsPerfCounters+0xf9b6
mscorwks.dll!CorExeMain+0x168
mscorwks.dll!CorExeMain+0x98
mscoree.dll!GetProcessExecutableHeap+0x4258
mscoree.dll!GetProcessExecutableHeap+0x2f00
mscoree.dll!CorExeMain+0x8

This occurs on the most recent version (released 3 Dec) as well.

I've now determined that problem occurs reliably after receiving a new message, and never recovers from the bad state.

Here's a little more info in case this is only occurring with a specific version of outlook:

Outlook Web Access version: 8.2.176.2
Exchange Client Access server .NET Framework version: 2.0.50727.3082
Client Access server operating system version: Microsoft Windows NT 5.2.3790 Service Pack 2
Client Access server operating system language: en-US
Microsoft Exchange Client Access server version: 8.2.176.0
Client Access server language: en-US
Microsoft Exchange Client Access server platform: 64bit
Mailbox server Microsoft Exchange version: 8.2.176.0

(This info was taken from the http://blah/owa/?ae=Options&
t=About page of OWA) In case Naresh can verify a similar version)

Chaps,

Does this happen on all combinations of notification type or just when Growl is switched on? I must admit I tend to use Snarl rather than Growl and have never seen this problem.

Please switch off all notification types and send some test email. Does the log show the new mail as is appears? Is the UI still sluggish at this point?

Would either of you be willing to be sent test versions of OWAtray to help me track this issue down?

Could I also ask one of you to install OWAtray cleanly on another PC and test whether you get the same behaviour. Thanks.

Naresh,

New version released tomorrow which should fix the problem you have.