Discussions related to HomeSeer Beta builds 3.0.0.369->3.0.0.423

[MNB]

Crash/Hang: Well it is day 4 and have just experienced an "HS3 has stopped working" message (crash/hang), according to HS3 System Uptime: 4 Days 6 Hours 36 Minutes XX Seconds of up time. Looking at the Win Event app it indicated the infamous “clr.dll” application Error.

I attempted to simply restart HS3.exe but it crash at the 90% according to the startup status green line, tried again with the same result. I then did a complete PC reboot and it came up, so I'm once again letting my system soak and will advise.

@Rich, anything you want to me to monitor? I looked at my Jon00perfmon metrics and they did not seem to be of anything to note, other than a very gradual reduction of System Physical Memory Available at 13,732 MB from a High of 14,392 MB whereas the System Virtual Memory increased from 2347 MB to 2948 MB. HomeSeer Virtual Memory increased to 191 MB from 82 MB

[bartbakels]

[Daweeze]

Ok, I crashed yesterday as well with the clr.dll problem....

Faulting application name: HS3.exe, version: 3.0.0.390, time stamp: 0x5a148ed8
Faulting module name: clr.dll, version: 4.7.2115.0, time stamp: 0x59af88f2
Exception code: 0xc00000fd

Restarted HS3 and up and running again.

Added a pic of the other items using CRL.DLL, not sure that it's useful.

-Travis

[rjh]

I really have no idea why this is happening, so I will need some help to narrow down what is causing it. A plan would be to disable plugins until it does not fail. If it still fails, disable some events. It has to be something that HS3 is doing that most people are not doing. It could be OS related, maybe a system update? the clr.dll is a .NET dll, so we at least know its related to the .net system.

Can you post the info from the help page.

Ok, I crashed yesterday as well with the clr.dll problem....

Faulting application name: HS3.exe, version: 3.0.0.390, time stamp: 0x5a148ed8
Faulting module name: clr.dll, version: 4.7.2115.0, time stamp: 0x59af88f2
Exception code: 0xc00000fd

Restarted HS3 and up and running again.

-Travis

[Daweeze]

Hey Rich,

Sure. Just note that I was running fine on all of the previous Beta's since 3.0.0.368 until now but I am keeping current to help troubleshoot these issues in the Beta that are popping up. That said, I did enable UltraMon again after I bought it during the sale last week and found EasyTrigger disabled and had enabled it a couple of days ago as well. Those are the only two variables besides version upgrades I have in mind for troubleshooting purposes.

Current Date/Time: 11/27/2017 1:28:11 PM
HomeSeer Version: HS3 Pro Edition 3.0.0.390
Operating System: Microsoft Windows 10 Pro - Work Station
System Uptime: 0 Days 20 Hours 25 Minutes 22 Seconds
IP Address: 192.168.5.3
Number of Devices: 914
Number of Events: 587
Available Threads: 400
HSTouch Enabled: False
Event Threads: 1
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Anti Virus Installed: Windows Defender

Enabled Plug-Ins
0.0.0.21: drhsIpPlugIn
3.0.0.41: EasyTrigger
3.0.0.25: ImperiHome
3.0.2.4: OMNI
0.0.0.35: Pushover 3P
3.0.5.5: SDJ-Health
3.0.6440.19101: UltraMon3
3.0.0.40: UPBSpud
3.0.1.162: Z-Wave

-Travis

[rjh]

If you are seeing a crash with clr.dll error, here is something you can run to help narrow down the issue. The error code reported indicates that the problem is a "stack overflow" error. Unfortunately the error does not have more information as to how this happened.

Microsoft has a tool that can monitor for a crash and then create a crash dump file that I might be able to analyze.

The tool is here:

https://www.microsoft.com/en-us/down....aspx?id=26798

Run it and follow the wizard to select the hs3.exe process to monitor. When it crashes, hopefully it will create a crash dump file.

[Daweeze]

If you are seeing a crash with clr.dll error, here is something you can run to help narrow down the issue. The error code reported indicates that the problem is a "stack overflow" error. Unfortunately the error does not have more information as to how this happened.

Microsoft has a tool that can monitor for a crash and then create a crash dump file that I might be able to analyze.

The tool is here:

https://www.microsoft.com/en-us/down....aspx?id=26798

Run it and follow the wizard to select the hs3.exe process to monitor. When it crashes, hopefully it will create a crash dump file.

Hi Rich,

I downloaded the tool and it's running. Hopefully we capture something a few days from now. It took HS3 about 4.5 days to reach the crashing point last time.

-Travis

[MNB]

It took HS3 about 4.5 days to reach the crashing point last time.

@Daweeze, that kind of spooky, as I too took 4.25 days to reach the crashing point.

[happnatious1]

Rich,

Is there a .390 for Linux? Is focus on windows first then Linux?

[randy]

Rich,

Is there a .390 for Linux? Is focus on windows first then Linux?

.387 is the latest beta. .390 was never announced, some enterprising individuals probed the HomeSeer server and found it. .388-.390 were one off Windows versions with additional logging to find a specific issue. I doubt they were ported to Linux.

[MNB]

@Rich, I too have download/installed the Debug tool, it is currently monitoring HS3.exe via a "Crash Rule for all instances of HS3.exe". As @Travis made mention earlier hopefully we will capture something of use in the near future (4 days from today). Mike

[MNB]

@Rich, I guess we didn't need to wait four days.. The attached is a zip of my debug files. I did not have a "HS3 has stopped working" message" this time in fact the HS3 icon wasn't in my tray but needless to say HS3 wasn't working around 9:50ish this morning up to then it was doing what was expected (morning events). The other thing is that I'm unable to get HS3 to stay running it goes through the start up and I see the log updating and was able whilst it was updating to manually turn on a light but the log would hang and there was no HS3 icon in the in tray. I even tried doing a POR and reboot the PC with the same results HS3 attempts to start up (log) but it simply disappears. And before you ask no I have not done anything HS3 related since restarting yesterday. I'm hoping that the debug files will provide some insight. Mike

[MNB]

@Rich, dumb question what is the mechanism (going on in the background) when I restart HS3.exe more than once, let's say if I restart HS3.exe three consecutive times in a row? The reason I'm asking is that I'm see a phenomena that after a crash that it takes more than once (sometimes) to properly get HS3 to restart. Are there files that rely on previously saved perimeters such as .ini or .dat files that if were not saved/shutdown correctly would (potentially) be flakey and not be able to startup properly, but if one starts the a second time the previously started .ini file is archived and another .ini is available and when a third restart of HS3 is attempted, HS3 comes up correctly? Mike

[rjh]

When HS3 starts it looks to see if there is an HS3.EXE already running, if so, it quits (might display a dialog). So I don't see a way for you to run it more than once.

@Rich, dumb question what is the mechanism (going on in the background) when I restart HS3.exe more than once, let's say if I restart HS3.exe three consecutive times in a row? The reason I'm asking is that I'm see a phenomena that after a crash that it takes more than once (sometimes) to properly get HS3 to restart. Are there files that rely on previously saved perimeters such as .ini or .dat files that if were not saved/shutdown correctly would (potentially) be flakey and not be able to startup properly, but if one starts the a second time the previously started .ini file is archived and another .ini is available and when a third restart of HS3 is attempted, HS3 comes up correctly? Mike

[MNB]

When HS3 starts it looks to see if there is an HS3.EXE already running, if so, it quits (might display a dialog). So I don't see a way for you to run it more than once.

Thanxs @Rich, I'm obviously grasping for straws... I would agree with you, if I did not restart the PC. Next time if it occurs, I will check Win Event monitor to verify. Mike