Running HS3 Pro for 15 days without a restart on .379 Raspberry Pi3 Raspbian Stretch with Mono 5.2. Memory usage has stabilised now.
Announcement
Collapse
No announcement yet.
Discussions related to HomeSeer Beta builds 3.0.0.369->3.0.0.423
Collapse
X
-
Two dumb questions ,
- Rich is this memory leak only associated with RPi community or is Windows also experiencing the same, and is this update for the RPi folks?
- I like the graphing that the RPi folks are displaying can the Windows folks do the same and if so how?
Thanxs MikeComputer: CUK Intel NUC7i7BNH
Op System: Windows10 Pro - Work Station
HS Version: HS4 Pro Edition 4.2.19.0
Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.
Comment
-
From the reports that I have seen, it looks like only Linux users are seeing a leak. So this build is targeted mainly for Linux users. I did post a Windows update also, it would be great for Windows users to update also just to make sure its ok.
Originally posted by MNB View PostTwo dumb questions ,
- Rich is this memory leak only associated with RPi community or is Windows also experiencing the same, and is this update for the RPi folks?
- I like the graphing that the RPi folks are displaying can the Windows folks do the same and if so how?
Thanxs Mike
Comment
-
Originally posted by concordseer View PostRunning HS3 Pro for 15 days without a restart on .379 Raspberry Pi3 Raspbian Stretch with Mono 5.2. Memory usage has stabilised now.
I am wondering if some of my events (300+) are still broken since the upgrade/migration to new Pi2 build (export/import of events). . .and the actual cause of the issue. . .any way to find just the ones that have missing devices/triggers?
Comment
-
Originally posted by rjh View PostFrom the reports that I have seen, it looks like only Linux users are seeing a leak. So this build is targeted mainly for Linux users. I did post a Windows update also, it would be great for Windows users to update also just to make sure its ok.
I'm going to start putting the Raspberry Pi3 through its paces and see how it holds up.
Comment
-
Originally posted by concordseer View PostRich I wonder if Linux users, particularly those on Raspberry Pi upgraded their Distro to Stretch and Mono to 5.2 or greater would this help. I'm running on Raspbian Stretch Mono 5.2 and it looks like, as you suggested, memory usage has stabilised.
I'm going to start putting the Raspberry Pi3 through its paces and see how it holds up.
Thanks,
Jim
Comment
-
Thank you Rich...
Updated Zee2 and HS3 Pro.
Current Date/Time: 11/7/2017 6:40:47 PM CST
HomeSeer Version: HS3 ZEE S2 Edition 3.0.0.383 (Linux)
HomeSeer: Is Registered
System Uptime: 0 Days 0 Hours 9 Minutes 41 Seconds
Homeseer touch is disabled.
Current Date/Time: 11/7/2017 6:42:38 PM CST
HomeSeer Version: HS3 Pro Edition 3.0.0.383 (Linux)
HomeSeer: Is Registered
System Uptime: 0 Days 0 Hours 2 Minutes 12 Seconds
Homeseer touch is enabled using 10-15 Wintel embedded tabletop tablets.
Both of the devices are now at:
ICS-HS3Pro:~# mono -V
Mono JIT compiler version 5.4.0.201 (tarball Fri Oct 13 21:51:45 UTC 2017)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
LLVM: supported, not enabled.
GC: sgen (concurrent by default)Last edited by Pete; November 7, 2017, 07:57 PM.- Pete
Auto matorHomeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
HS4 Pro - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant
Comment
-
Originally posted by Pete View PostThe RPi3 Zee2 image is using Jessie Lite and not sure on the Mono version.HomeSeer Version: HS3 Standard Edition 3.0.0.548
Linux version: Linux auto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Number of Devices: 484 | Number of Events: 776
Enabled Plug-Ins: 3.0.0.13: AirplaySpeak | 2.0.61.0: BLBackup
3.0.0.70: EasyTrigger | 1.3.7006.42100: LiftMaster MyQ
4.2.3.0: mcsMQTT | 3.0.0.53: PHLocation2 | 0.0.0.47: Pushover 3P
3.0.0.16: RaspberryIO | 3.0.1.262: Z-Wave
Z-Net version: 1.0.23 for Inclusion Nodes
SmartStick+: 6.04 (ZDK 6.81.3) on Server
Comment
-
Thank you Timon
Here updating Mono from 4.X to 5.4 did not effect any of my events / triggers.
Only time I have seen the updating of Mono messing with my stuff was in the early days of using Mono 3.28 to updating to Mono 3.12.- Pete
Auto matorHomeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
HS4 Pro - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant
Comment
-
so @concordseer is correct. my RPI was set with a system locale of EN_GB. raspi-config wouldn't override this. i ended up having to run
sudo dpkg-reconfigure locales, uncheck en_GB, and checked en_US... then rebooted the system. that fixed my date rendering from DD/MM/YYYY to MM/DD/YYYY.
I also spent the evening grabbing screenshots of my events and exporting the events as is. I am going to take my last image of the system and perform the mono update. i will report back once complete.
Comment
-
After 8 hours here using V.383 memory usage went down from startup.
Note I am still utilizing the Pine64 2 Gb machine here (not the RPi). First time I have seen HConsole run under a Mb on the Pine64 with Ubuntu 16.04 64bit.
[ATTACH]64335[/ATTACH]Last edited by Pete; November 8, 2017, 07:47 AM.- Pete
Auto matorHomeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
HS4 Pro - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant
Comment
-
Ok, I had gone back to v.368 (a few days ago) and am experiencing what looks like a memory leak within HS3 Windows Pro. I've included resource monitoring snap shots of this mornings anemic operating HS3. It looks like the HS Log stopped updating at around 5:29 am (last entry) this morning, quick review did not have any error/warning messages. My morning "school wake up announcement" event did not work, but my hourly chime and time announced event did which are both set for 7:00 am. My HSM200 seemed to be working (7:10 am) because they changed colors when motion was sensed and the associated actions (turn light(s) on) worked. When I reviewed my HS3 machine I had the following error;
11/8/2017 7:36:21 AM
Exception of type 'System.OutOfMemoryException' was thrown.
HomeSeer version: 3.0.0.368
Source: Scheduler
Target: Void .ctor()
Stack trace:
at Scheduler.StateObject..ctor()
at Scheduler.Web_Server.AcceptCallback(IAsyncResult ar)
at Org.Mentalis.Security.Ssl.AsyncResult.Notify(Exception e)
at Org.Mentalis.Security.Ssl.AsyncResult.Notify()
at Org.Mentalis.Security.Ssl.SecureSocket.OnAccept(IAsyncResult ar)
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Net.ContextAwareResult.CompleteCallback(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionConte xt executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.ContextAwareResult.Complete(IntPtr userToken)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
at System.Net.Sockets.Socket.AcceptCallback(Object nullState)
at System.Net.Sockets.Socket.RegisteredWaitCallback(Object state, Boolean timedOut)
at System.Threading._ThreadPoolWaitOrTimerCallback.PerformWaitO rTimerCallback(Object state, Boolean timedOut)
Please specify what you were doing at the time of this error:
After doing a System Restart, I added the resource monitoring snapshots; The second three graphics (combined), (CPU), (Memory). Note HS3.exe file size 167,932 (KB) a 7.7x reduction.
From my novice opinion, "Houston, we have" an MEMORY LEAK that in my case seems to happen every 2nd day. Looking at my latest (11:08 am) Memory status I'm now up to 321,208 (KB).
I've also included my HS3;
System Profile
Current Date/Time: 11/8/2017 11:09:35 AM
HomeSeer Version: HS3 Pro Edition 3.0.0.368
Operating System: Microsoft Windows 10 Pro - Work Station
System Uptime: 0 Days 3 Hours 22 Minutes 44 Seconds
IP Address: 192.168.0.55
Number of Devices: 537
Number of Events: 208
Available Threads: 400
Enabled Plug-Ins
2.0.48.0: BLBackup
2.0.40.0: BLGData
2.0.12.0: BLRoombaWifi
3.1.1.24385: Blue-Iris
3.0.0.40: EasyTrigger
3.0.0.24: ImperiHome
3.0.0.28: Nest
3.0.1.109: PHLocation
0.0.0.34: Pushover 3P
3.0.0.1: Random
1.0.0.5: Restart
3.1.0.22: Sonos
3.0.6331.36036: UltraCID3
3.0.6519.37235: UltraWeatherWU3
3.0.1.152: Z-WaveSystem Information
Current Date/Time: 11/8/2017 11:11:38 AM Eastern Standard Time
HomeSeer Version: HS3 Pro Edition 3.0.0.368 (Windows)
HomeSeer: Is Registered
Operating System: Microsoft Windows 10 Pro - Work Station
OS Version: 10.0.16299 Service Pack: 0.0
System Uptime: 0 Days 3 Hours 24 Minutes 47 Seconds
User Name and Access Level: MNB (Admin)
LAN IP Address:
Client IP Address:
External IP Address:
Network Adapter: Adapter -> Intel(R) Ethernet Connection (4) I219-V IP: 192.168.0.XX/24 MAC: 94:C6:91:10:EE:B4
Network Adapter: HomeSeer Adapter -> Loopback Address (localhost) IP: 127.0.0.1
Web Server Port: XXXX
Number of Devices: 537
Number of Events: 208
Event Last Ran: Network : Network Monitoring, Ran at 11/8/2017 11:11:09 AM
Number of unique event scripts used: 1
Connected Speaker Clients: LMBHOMESEER (127.0.0.1)EFAULT
Plug-Ins Enabled: Restart:,Pushover 3P:,Nest:,BLGData:,UltraCID3:,ImperiHome:,Blue-Iris:,Random:,BLRoombaWifi:,Sonos:,EasyTrigger:,Z-Wave:,UltraWeatherWU3:,PHLocation:,BLBackup:
Processor Type and Speed: Intel64 Family 6 Model 142 Stepping 9 at 3.26 GHz
Modules/Threads: 140 Modules, 156 Threads
Available Threads: 400
System Processes/Load: 155 Processes, 4% Load
Free / Total Physical Memory: 13.14 GBytes / 15.89 GBytes (83% free)
Free / Total Virtual Memory: 15.44 GBytes / 18.27 GBytes (85% free)
HomeSeer Memory Used: 312 Mbytes
Plug-In Memory Used: 15 EXE Plug-Ins using 557 MbytesLast edited by MNB; November 8, 2017, 03:54 PM.Computer: CUK Intel NUC7i7BNH
Op System: Windows10 Pro - Work Station
HS Version: HS4 Pro Edition 4.2.19.0
Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.
Comment
-
Originally posted by rjh View PostIf you are seeing a memory leak can you please update to build 383 and see if there is any change.
I did find a thread in HSTouch that was allocating memory every 10 seconds and it might not have been freed. That is fixed in build 383 which is posted.
https://forums.homeseer.com/showthread.php?t=181241
Comment
-
We know there are some possible issues with previous builds, if you are going to do some testing, please run the latest beta as I cannot debug any previous builds. 383 is the latest as of this post.
Originally posted by MNB View PostOk, I had gone back to v.368 (a few days ago) and am experiencing what looks like a memory leak within HS3 Windows Pro. I've included resource monitoring snap shots of this mornings anemic operating HS3. It looks like the HS Log stopped updating at around 5:29 am (last entry) this morning, quick review did not have any error/warning messages. My morning "school wake up announcement" event did not work, but my hourly chime and time announced event did which are both set for 7:00 am. My HSM200 seemed to be working (7:10 am) because they changed colors when motion was sensed and the associated actions (turn light(s) on) worked. When I reviewed my HS3 machine I had the following error;
I've included snapshots of my HS3 resource monitor during the System Error; The first three graphics, (combined), (CPU), (Memory). Note the bloated HS3.exe file size 1,309,704 (KB).
After doing a System Restart, I added the resource monitoring snapshots; The second three graphics (combined), (CPU), (Memory). Note HS3.exe file size 167,932 (KB) a 7.7x reduction.
From my novice opinion, "Houston, we have" an MEMORY LEAK that in my case seems to happen every 2nd day. Looking at my latest (11:08 am) Memory status I'm now up to 321,208 (KB).
I've also included my HS3;
I'm thinking about trying out v.383 @Rich do you advise the same? Mike
Comment
Comment