Some users of the mcsTemperature plugin are experiencing lockup-type conditions when exiting the setup page associated with the plugin. Detailed debug statements have been inserted and a trace log using hs.debug also produced with no evidence of the source of the problem.
The plugin code invloved consists of a form with a load procedure, an unload procedure, and a cancel (or update) button. The code is as follows:
<pre class="ip-ubbcode-code-pre">
hspi_mcstemperature Class called by homeseer when user selects Setup button
------------------------
Public Sub ConfigIO()
Dialog.Show vbModal
End Sub
dialog form
------------
Private Sub Form_Load()
On Error GoTo Error_Exit
<initialize bunch of global variables>
Normal_Exit:
Exit Sub
Error_Exit:
hs.writelog "mcsTemperature Plugin", "Setup Load: " & Err.description
Resume Normal_Exit
End Sub
Private Sub Form_unload(Cancel As Integer)
End Sub
cancel button on dialog form
----------------------------
Private Sub CancelButton_Click()
On Error Resume Next
hs.writelog "debug","Before Unload"
Unload Me
hs.writelog "debug","After Unload"
End Sub
</pre>
The homeseer log shows the two debug statements being executed as a result of the cancel button being clicked. It then shows that it is shutting down and then startup messages appear for the mcsTemperature and the MR26 plugins (both .exe plugins). This sequence is also accompanied by a windows message like "Switch-to or Retry" because the application is not responding.
The homeseer trace log also shows the normal actions being performed by the mcsTemperature plugin on 1 minute intervals based upon an internal timer within the plugin. It is the act of trying to close the setup page that induces the failure modes.
Any suggestions as to what could be happening?
A second odd behavior, that apparrently only I have observed is at the startup of homeseer. A splash screen appears and in the past it would normally exists for only a few seconds. It now remains up for 3 minutes with the status lines showing "Checking HSPIMCSTEMPERATURE.hspi". During this 3 minute period I can observe the mcsTemperature.exe process running with about 2M or memory utilized. Debug statements were included in every entry point that homeseer may reference, including Class_Initialize. None of these were entered during this 3 minute period.
After the 3 minute period the memory use goes up to around 8M.
I also observed that plugins were being checked that I have previously installed but since have removed. I also removed the .exe/.ocx from the directory. It appears that once a plugin is installed homeseer will then always be looking for it even if it no longer exists on the computer.
The 3 minute startup does not affect the operation, but it is an annoyance.
What is homeseer really doing when it shows the "checking" message?
The plugin code invloved consists of a form with a load procedure, an unload procedure, and a cancel (or update) button. The code is as follows:
<pre class="ip-ubbcode-code-pre">
hspi_mcstemperature Class called by homeseer when user selects Setup button
------------------------
Public Sub ConfigIO()
Dialog.Show vbModal
End Sub
dialog form
------------
Private Sub Form_Load()
On Error GoTo Error_Exit
<initialize bunch of global variables>
Normal_Exit:
Exit Sub
Error_Exit:
hs.writelog "mcsTemperature Plugin", "Setup Load: " & Err.description
Resume Normal_Exit
End Sub
Private Sub Form_unload(Cancel As Integer)
End Sub
cancel button on dialog form
----------------------------
Private Sub CancelButton_Click()
On Error Resume Next
hs.writelog "debug","Before Unload"
Unload Me
hs.writelog "debug","After Unload"
End Sub
</pre>
The homeseer log shows the two debug statements being executed as a result of the cancel button being clicked. It then shows that it is shutting down and then startup messages appear for the mcsTemperature and the MR26 plugins (both .exe plugins). This sequence is also accompanied by a windows message like "Switch-to or Retry" because the application is not responding.
The homeseer trace log also shows the normal actions being performed by the mcsTemperature plugin on 1 minute intervals based upon an internal timer within the plugin. It is the act of trying to close the setup page that induces the failure modes.
Any suggestions as to what could be happening?
A second odd behavior, that apparrently only I have observed is at the startup of homeseer. A splash screen appears and in the past it would normally exists for only a few seconds. It now remains up for 3 minutes with the status lines showing "Checking HSPIMCSTEMPERATURE.hspi". During this 3 minute period I can observe the mcsTemperature.exe process running with about 2M or memory utilized. Debug statements were included in every entry point that homeseer may reference, including Class_Initialize. None of these were entered during this 3 minute period.
After the 3 minute period the memory use goes up to around 8M.
I also observed that plugins were being checked that I have previously installed but since have removed. I also removed the .exe/.ocx from the directory. It appears that once a plugin is installed homeseer will then always be looking for it even if it no longer exists on the computer.
The 3 minute startup does not affect the operation, but it is an annoyance.
What is homeseer really doing when it shows the "checking" message?
Comment