JowiHue crashes when HS3 is shutting down

[teladog01]

Many times, but not every time, the JowiHue plugin crashes when I shutdown HS3. This has been an ongoing issue for quite a while since I migrated my HS3 install to a VM running Server 2012 R2. The plugin seems to work fine otherwise and I haven't had any crashes other than when HS3 is shutting down. I have installed the latest .NET updates, currently 4.6.2.

Here is the full text in the crash notification window:

Problem signature:
  Problem Event Name:	CLR20r3
  Problem Signature 01:	HSPI_JowiHue.exe
  Problem Signature 02:	1.1.2.6
  Problem Signature 03:	583d8c72
  Problem Signature 04:	mscorlib
  Problem Signature 05:	4.6.1087.0
  Problem Signature 06:	583e5abb
  Problem Signature 07:	59df
  Problem Signature 08:	13
  Problem Signature 09:	System.NullReferenceException
  OS Version:	6.3.9600.2.0.0.272.7
  Locale ID:	1033
  Additional Information 1:	5861
  Additional Information 2:	5861822e1919d7c014bbb064c64908b2
  Additional Information 3:	6ee2
  Additional Information 4:	6ee2432e64e99bdcea5e4be767a3b1a2

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=280262

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

There are two events logged in the Application event log:

Event 1026, .NET Runtime

Application: HSPI_JowiHue.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
   at System.Runtime.Remoting.Messaging.LogicalCallContext.PropagateIncomingHeadersToCallContext(System.Runtime.Remoting.Messaging.IMessage)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(System.Runtime.Remoting.Proxies.MessageData ByRef, Int32)
   at HomeSeerAPI.IHSApplication.WriteLog(System.String, System.String)
   at HSPI_JowiHue.utils.Log(System.String, LogLevel)
   at HSPI_JowiHue.BridgeCache.UpdateBridgeCache()
   at HSPI_JowiHue.BridgeCache._Lambda$__R31-1(System.Object)
   at System.Threading.TimerQueueTimer.CallCallbackInContext(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.TimerQueue.FireNextTimers()
   at System.Threading.TimerQueue.AppDomainTimerCallback()

Event 1000, Application Error

Faulting application name: HSPI_JowiHue.exe, version: 1.1.2.6, time stamp: 0x583d8c72
Faulting module name: mscorlib.ni.dll, version: 4.6.1590.0, time stamp: 0x5787ed44
Exception code: 0xc0000005
Fault offset: 0x003d0ea2
Faulting process id: 0x688
Faulting application start time: 0x01d2809c55950927
Faulting application path: C:\Program Files (x86)\HomeSeer HS3\HSPI_JowiHue.exe
Faulting module path: C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\7582400666d289c016013ad0f6e0e3e6\mscorlib.ni.dll
Report Id: 2c96e687-ec90-11e6-80ef-000c29da2296
Faulting package full name: 
Faulting package-relative application ID:

[w.vuyk]

teladog01,

I thought I had caught all variations already a few versions ago. Apparently not . Closing the plugin once HS3 closes is done in a very short and narrow time window. HS3 is quite demanding in that area On my system I did test this very frequent and deep and I cannot copy this issue.

What are the specs on your HS3 server, is it extreme fast maybe? I am testing on a slow and 'normal ' machine, not seeing this issue.

I will check later again, for the time being you can prevent the popup by changing the error reporting options in your system.

Thanks,

Wim

[teladog01]

What are the specs on your HS3 server, is it extreme fast maybe? I am testing on a slow and 'normal ' machine, not seeing this issue.

It is a VM with 2 cores of an i7 and 4 GB RAM. The hard disk is just SATA iSCSI (not SSD). Overall I would say it is pretty "normal" performance-wise.

I will check later again, for the time being you can prevent the popup by changing the error reporting options in your system.

If this is not an issue for the plugin then I will just disable the error reporting. But I wanted to let you know about the issue.

Thanks!

[w.vuyk]

It is an issue for the plugin, but will not occur for everyone, and it might be some time before I will be able to catch it

Wim

[DSteiNeuro]

I get this also from time to time, but have just ignored it and try to allow a couple of seconds before a restart.

MSI Cubi Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz, 2201 Mhz, 2 Core(s), 4 Logical Processor(s) 16GB DDRl RAM