Discussions related to HS3 build 3.0.0.368

[racerfern]

Since I'm on .368 I'll also post here.

Z-tool+ is not seeing my system. JSON is checked, UPNP is checked. HSTouch works but not ztool.

[S-F]

I'm still on .374. I'm running about one million plugins and scripts. My up time is just over 3 days. Memory usage is stable at just under 80 MB. Some times it's higher. Some times it's lower. But never by too much in either direction. So, it would appear that any issues are specific to either a certain OS or plugin that I'm not using. Just like my lost hair and the death of my childhood dog I'm going to blame Windows 10 for this.

[rjh]

There is definitely a memory leak in 376 (that I introduced) with regards to the log, so if you run 376 you really need to disable the log in order to test.

I've been running .376 now since last night. The memory is increasing very slowly, but I have not disabled logging yet. This is the best it has been. Tomorrow I will enable more plugins.

[rjh]

I guess at this point I would be most concerned with a crash. Memory is hard to quantify since as Jon00 mentions .net cleans up the memory when it feels like it. If you have a system with a lot of Ram it may allow memory to climb higher than a system with little ram.

But I have fixed a few small issues since 374 and I would like you to test with 376 with the log off. The log is fixed in 377 so you can update to this build and leave the log on. I uploaded Linux builds also:

http://homeseer.com/updates3/SetupHS3_3_0_0_377.msi

[Guest]

The log is fixed in 377 so you can update to this build and leave the log on. I uploaded Linux builds also:

Installed 377 on my SEL but it's showing version 376 in setup.

[Pete]

Thank you Rich.

Updated three machines here at ~1130 c time - 14th of October, 2017

1 - HS3 ZEE S2 Edition 3.0.0.377 (Linux)
Ubuntu 16.04 64bit 2Gb RAM - dual core AMD
Mono - Mono JIT compiler version 5.2.0.224 - 64bit
Available Threads:200
HomeSeer Memory Used:115 Mbytes

HS3ZeeLite:~# free -m
              total        used        free      shared  buff/cache   available
Mem:           1745         538         720          14         486        1032
Swap:          1788           0        1788

2 - HS3 ZEE S2 Edition 3.0.0.377 (Linux)
Ubuntu 16.04 64bit 2Gb RAM - quad core ARM
Mono - Mono JIT compiler version 5.2.0.224 64bit
Available Threads:399
HomeSeer Memory Used:79 Mbytes

Pine64:~# free -m
              total        used        free      shared  buff/cache   available
Mem:           1988         250        1481           8         256        1696
Swap:           994           0         994

3 - HS3 Pro Edition 3.0.0.377 (Linux)
Ubuntu 16.04 64bit 16Gb RAM - quad core Intel
Mono - Mono JIT compiler version 5.2.0.224 - 64bit
Available Threads:400
HomeSeer Memory Used: 135 Mbytes

HS3Pro:~# free -m
              total        used        free      shared  buff/cache   available
Mem:          15935        5339        9270          91        1325       10166
Swap:         16269           0       16269

Computers #1 and #2 are running identical HS3 configurations.
Curious a bit about available threads and HS memory usage being different.
Updated mono to Mono JIT compiler version 5.2.0.224 on the three boxes.

[rjh]

I rebuilt it and uploaded again, its 377 now so you should re-apply the update.

Installed 377 on my SEL but it's showing version 376 in setup.

[rjh]

Available threads is based on system resources, are both those computers identical in terms of memory?

Thank you Rich.

Updated three machines here at ~1130 c time - 14th of October, 2017

1 - HS3 ZEE S2 Edition 3.0.0.377 (Linux)
Ubuntu 16.04 64bit 2Gb RAM - dual core AMD
Mono - Mono JIT compiler version 4.2.1 64bit
Available Threads:200
HomeSeer Memory Used:115 Mbytes

2 - HS3 ZEE S2 Edition 3.0.0.377 (Linux)
Ubuntu 16.04 64bit 2Gb RAM - quad core ARM
Mono - Mono JIT compiler version 5.2.0.224 64bit
Available Threads:399
HomeSeer Memory Used:79 Mbytes

3 - HS3 Pro Edition 3.0.0.377 (Linux)
Ubuntu 16.04 64bit 16Gb RAM - quad core Intel
Mono - Mono JIT compiler version 4.2.1 64bit
Available Threads:400
HomeSeer Memory Used: 135 Mbytes

Computers #1 and #2 are running identical HS3 configurations.
Curious a bit about available threads and HS memory usage being different.

[jlrichar]

That would be a good find, but I checked the code and the first thing it does is check if the device to be controlled exists, if not, it does nothing. So I don't see how this would have affected anything.

Its possible the events are not being loaded properly due to the changes I made to import/export events as json. I have backed out those changes and posted a build 375 to test that theory. So anyone seeing a memory leak, please try build 375 and see if the leak still exists.

In your case, editing the events may have removed some of the events that were not loaded properly.

I am still on 374, and homeseer memory is still @ 40ish MB. It seems stable to me. Since I was definitely experiencing the problem, and now I am not it is possible that something I did when I updated to 374 fixed the issue for my current HS3 session. Something else I did, that I did not mention previously is I opened each event, and each event group conditions to confirm that there were no missing devices. Perhaps the act of opening each one removed some corruption carried over from a previous version? Is there a way to programattically do this during the version update?

Current Date/Time: 10/14/2017 11:00:20 AM
HomeSeer Version: HS3 Pro Edition 3.0.0.374
Operating System: Microsoft Windows Server 2012 Standard - Server
System Uptime: 2 Days 12 Hours 48 Minutes 11 Seconds
IP Address: 192.168.1.105
Number of Devices: 708
Number of Events: 172
Available Threads: 200
Event Threads:2
Event Trigger Eval Queue:0
Event Trigger Priority Eval Queue:0
Device Exec Queue:0
Plugin Callback Queue:0
HSTouch Event Queue:0
Email Send Queue:0

Enabled Plug-Ins
3.2.0.5: APCUPSD
3.0.0.18: DirecTV
3.0.0.40: EasyTrigger
0.0.0.3: Garadget 3P
3.0.1.3: IFTTT
3.0.0.24: ImperiHome
1.1.3.1: JowiHue
2.17.0.18: MCSSPRINKLERSS
1.0.15132.98: MPower
3.0.0.28: Nest
3.0.1.83: PHLocation
3.0.0.5: Pushalot
0.0.0.34: Pushover 3P
30.0.0.35: RFXCOM
3.1.0.22: Sonos
3.0.6132.16975: UltraGCIR3
3.0.6440.19101: UltraMon3
3.0.0.40: UPBSpud
3.0.0.73: weatherXML
3.0.1.130: Z-Wave

[Pete]

Available threads is based on system resources, are both those computers identical in terms of memory?

Yes.

Odd that one is a dual core AMD (Xi5a Cube) and the other is a quad core ARM (Pine64) with same memory / same drive space of 32Gb.

Both are running Ubuntu 16.04 64bit with 2Gb of RAM.

[scorp508]

.376 has been running here on Windows 10 for ~45 hours and hs3.exe is holding at approximately 36.5 MB.

Current Date/Time: 10/14/2017 2:42:45 PM
HomeSeer Version: HS3 Pro Edition 3.0.0.376
Operating System: Microsoft Windows 10 Enterprise - Work Station
System Uptime: 1 Day 21 Hours 41 Minutes 46 Seconds
Number of Devices: 419
Number of Events: 62
Available Threads: 400
Event Threads:0
Event Trigger Eval Queue:0
Event Trigger Priority Eval Queue:0
Device Exec Queue:0
Plugin Callback Queue:0
HSTouch Event Queue:0
Email Send Queue:0

Enabled Plug-Ins
3.2.0.5: APCUPSD
2.0.47.0: BLBackup
3.0.0.37: EasyTrigger
3.0.0.20: Ecobee
3.0.0.38: EnvisaLink
1.1.3.1: JowiHue
3.0.0.14: NetCAM
0.0.0.34: Pushover 3P
3.0.0.73: weatherXML
3.0.1.130: Z-Wave

[zzapper77]

Just FYI: Restored my vm back to .357 and everything runs smoothly again. Rules out faulty hardware.

[scooter]

First graph tick is 3.0.0.368 crash. Second tick is the reboot with 3.0.0.377.



Current Date/Time: 10/14/2017 5:10:09 PM
HomeSeer Version: HS3 Pro Edition 3.0.0.377
Operating System: Microsoft Windows 7 Professional - Work Station
System Uptime: 0 Days 6 Hours 20 Minutes 31 Seconds
IP Address: 192.168.1.130
Number of Devices: 292
Number of Events: 62
Available Threads: 400
HSTouch Enabled:True
Event Threads:2
Event Trigger Eval Queue:0
Event Trigger Priority Eval Queue:0
Device Exec Queue:0
Plugin Callback Queue:0
HSTouch Event Queue:0
Email Send Queue:0

Enabled Plug-Ins
2.0.47.0: BLBackup
1.1.11.0: Honeywell WiFi Thermostat
3.0.1.3: IFTTT
3.0.6.0: Insteon
1.1.3.1: JowiHue
1.1.17267.112: MyQ
3.0.0.28: Nest
0.0.0.34: Pushover 3P
3.0.6104.19146: UltraRachio3
3.0.1.130: Z-Wave

Sent from my Moto Z (2) using Tapatalk

[scooter]

1st tick is 3.0.0.368 crash, 2nd is restart with 3.0.0.377.



Sent from my Moto Z (2) using Tapatalk

[Pete]

@Scooter
Suggestion: blur out your dynamic DNS address.