Announcement

Collapse
No announcement yet.

Discussions related to HomeSeer Beta builds 3.0.0.369->3.0.0.423

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Might be helpful or not but can say that I'm now on 4 days 12 hours and HS is sitting quite happily at 107MB (on the about page) which is slightly more than it was but not something I am going to worry about. Task Manager reports 60MB so something slightly strange (guess it's a different set of memory it is reporting) there but either way I'm OK.

    Comment


      Originally posted by mrhappy View Post
      Might be helpful or not but can say that I'm now on 4 days 12 hours and HS is sitting quite happily at 107MB (on the about page) which is slightly more than it was but not something I am going to worry about. Task Manager reports 60MB so something slightly strange (guess it's a different set of memory it is reporting) there but either way I'm OK.

      At the risk of spamming this thread I'm on .382 with an uptime of just over two days. The about page shows 127 MB used, which is lower than it was initially, and task manager shows 80. Running Windows here.
      Originally posted by rprade
      There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

      Comment


        Ran .379 for 15 days without a crash. Stopped it to update to .383 today to help with testing. Memory usage rising at its usual rate on startup, I'm going to leave this one running until memory usage settles or it crashes.

        I think these updates are aimed at Linux users. Has it now been established that Windows users memory issues have been resolved. Still puzzled as to why memory usage steadily rises from startup. Should memory be rising and falling as processes are swapped in and out of memory as and when they are utilised. Maybe this is a too simplistic way of looking at things.
        Last edited by concordseer; November 8, 2017, 07:56 PM. Reason: Typo

        Comment


          Ok, I have just updated to v.383 (11/8/17). After doing a System Restart, I've captured my initial resource monitoring snapshots of; (combined), (CPU), (Memory). Note HS3.exe file size is currently ~126,860 (KB) per Windows Resource Monitor and 124 Mbytes per HS3 (delta of 2 MB).

          Current Date/Time: 11/8/2017 7:47:25 PM Eastern Standard Time
          HomeSeer Version: HS3 Pro Edition 3.0.0.383 (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 0 Hours 14 Minutes 0 Seconds
          User Name and Access Level: MNB (Admin)
          LAN IP Address: 192.168.0.XXX (LMBHomeSeer)
          Client IP Address: 192.168.0.XXX (LMBFarms)
          External IP Address:
          Network Adapter: Adapter -> Intel(R) Ethernet Connection (4) I219-V IP: 192.168.0.XXX/XXX MAC: 94:C6:91:10:EE:B4
          Network Adapter: HomeSeer Adapter -> Loopback Address (localhost) IP: 127.0.0.1
          Web Server Port: XXX
          Number of Devices: 537
          Number of Events: 208
          Event Last Ran: Weather : Weather Condition - Not Clear, Ran at 11/8/2017 7:47:26 PM
          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: 151 Modules, 176 Threads
          Available Threads: 400
          System Processes/Load: 160 Processes, 2% Load
          Free / Total Physical Memory: 13.50 GBytes / 15.89 GBytes (85% free)
          Free / Total Virtual Memory: 15.76 GBytes / 18.27 GBytes (86% free)
          HomeSeer Memory Used: 124 Mbytes
          Plug-In Memory Used: 15 EXE Plug-Ins using 586 Mbytes
          Will keep track to ensure Memory Leak is contained. Mike
          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 Furious View Post
            Nope, still the same - installed, enabled logging, 4 hours later memory used is now 1GB higher than when first loaded.
            Same here. Memory is increasing slowly, but still increasing. From around 96MB real at startup last night, to 196MB real now (322MB virtual). But this is short term and may be normal. I'll keep it going and see what happens. But I still have the callback queue issue with a couple of plugins that I have disabled.

            Comment


              Do we have a running list of Plugin's that cause "callback queue issue"?
              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


                HS3 Crash 4 mornings in a row

                Four mornings in a row I wake up and HS3 has crashed. This started when I upgraded to .382 so I then upgraded to .383 and have the same problem.
                I could not find anything in HS3 log so I coped the windows error and attached it.

                MESSAGE BOARD (copy/paste section below to message board posts)

                Current Date/Time: 11/9/2017 8:53:10 AM
                HomeSeer Version: HS3 Standard Edition 3.0.0.383
                Operating System: Microsoft Windows Embedded Standard - Work Station
                System Uptime: 0 Days 2 Hours 10 Minutes 38 Seconds
                IP Address: 192.168.1.182
                Number of Devices: 573
                Number of Events: 65
                Available Threads: 200
                HSTouch Enabled: True
                Event Threads: 0
                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:

                Enabled Plug-Ins
                3.2.0.5: APCUPSD
                2.0.8.0: BLCpuAdvisor
                2.0.35.0: BLLAN
                1.0.3.0: BLShutdown
                3.0.0.101: LutronCaseta
                0.0.0.34: Pushover 3P
                3.0.6331.36036: UltraCID3
                3.0.5917.35093: UltraLog3
                3.0.6370.28796: UltraM1G3
                3.0.6440.19101: UltraMon3
                3.0.0.77: weatherXML
                3.0.1.152: Z-Wave
                Attached Files

                Comment


                  Not sure on this one, this is the first report I have seen that references the clr.dll. That DLL is a core .NET dll so this crash was in .NET. I assume you are not running any third party anti virus so we can rule that out?

                  A quick google search finds some references to this type of crash and different fixes from hotfixes to a .NET installation error.

                  Do you have another PC you can copy your config over to so we can rule out a PC issue?

                  Originally posted by ralnet View Post
                  Four mornings in a row I wake up and HS3 has crashed. This started when I upgraded to .382 so I then upgraded to .383 and have the same problem.
                  I could not find anything in HS3 log so I coped the windows error and attached it.

                  MESSAGE BOARD (copy/paste section below to message board posts)

                  Current Date/Time: 11/9/2017 8:53:10 AM
                  HomeSeer Version: HS3 Standard Edition 3.0.0.383
                  Operating System: Microsoft Windows Embedded Standard - Work Station
                  System Uptime: 0 Days 2 Hours 10 Minutes 38 Seconds
                  IP Address: 192.168.1.182
                  Number of Devices: 573
                  Number of Events: 65
                  Available Threads: 200
                  HSTouch Enabled: True
                  Event Threads: 0
                  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:

                  Enabled Plug-Ins
                  3.2.0.5: APCUPSD
                  2.0.8.0: BLCpuAdvisor
                  2.0.35.0: BLLAN
                  1.0.3.0: BLShutdown
                  3.0.0.101: LutronCaseta
                  0.0.0.34: Pushover 3P
                  3.0.6331.36036: UltraCID3
                  3.0.5917.35093: UltraLog3
                  3.0.6370.28796: UltraM1G3
                  3.0.6440.19101: UltraMon3
                  3.0.0.77: weatherXML
                  3.0.1.152: Z-Wave
                  💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

                  Comment


                    Googling here a bit and seeing something similiar (not sure what that something is) and could be related to a 3rd party application running. Just another google effort here...

                    I have two computers. Both work under Windows 7 Embedded and have same version of .Net 4.0 framework installed. My WinForms application works with no issues on one of them but fails at start-up with BEX in clr.dll on another.


                    Solution finally found

                    My application uses third party C# library which is actually a wrapper on top of calls to other native library. I decompiled library and realised that calling convention is set to CallingConvention.Cdecl but as I see from Dependency Walker application, all methods in native library has CallingConvention.StdCall

                    After changing calling convention and recompiling the library issue disappeared.
                    - Pete

                    Auto mator
                    Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                    Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                    HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

                    HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                    HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

                    X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                    Comment


                      I am not sure why I would move the config file to another computer because I am on an S6 Standard and only log in via the web and I do not have HS3 on any PC. I am runing Norton Security.
                      Last edited by ralnet; November 9, 2017, 10:24 AM.

                      Comment


                        The AV stuff relating to Windows in general (lately with Windows 10) has historically been an issue.

                        The S6 W7 embedded is really not too changeable but you can add a 3rd party W7 application easy enough.

                        The above posted issue in post # 130 related to an add of a font (which really shouldn't be an issue).

                        and above we see the mention of a dot net fix.

                        There are Microsoft tools out there which will look at your DOT NET stuff and fix it or re-install it which may fix your issue.

                        Microsoft .NET Framework Repair Tool
                        - Pete

                        Auto mator
                        Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                        Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                        HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

                        HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                        HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

                        X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                        Comment


                          I am on 3.0.0.382 about screen shows up for 1 Day 7 Hours 15 Minutes 27 Seconds.
                          Memory utilization is steady 76 Mbytes.
                          359 devices
                          180 events
                          3 scripts.

                          HS3 is Running on an RPI 3. Raspbian Jessie Lite with Mono version 3.12.


                          Sent from my iPhone using Tapatalk

                          Comment


                            Originally posted by concordseer View Post
                            Ran .379 for 15 days without a crash. Stopped it to update to .383 today to help with testing. Memory usage rising at its usual rate on startup, I'm going to leave this one running until memory usage settles or it crashes.

                            I think these updates are aimed at Linux users. Has it now been established that Windows users memory issues have been resolved. Still puzzled as to why memory usage steadily rises from startup. Should memory be rising and falling as processes are swapped in and out of memory as and when they are utilised. Maybe this is a too simplistic way of looking at things.
                            Well, since I've had a massive memory leak with logging on ever since HSTouch was integrated, I'd like to know what I can actually check as apart from installing MS updates, the server has had nothing else done to it.

                            Comment


                              Updated to Beta v383 at 7:55 pm 11/8/17 with my HS3.exe working memory around 133,096 (KB). Looking at my HS3.exe working memory at 11:18 am 11/9/17 it's hovering around 147,700 to 154,388 (KB), so the memory leak seems to be holding (fingers crossed).

                              Looking at the "Manage Plugin" tab the installed plugin versions are still missing in the "Installed" column.

                              One minor observation I've noticed is that my HSM200 response time seems to be slightly slower than the have prior to this version.

                              I've included two Jon's Performance Monitoring graphics; one is with v.368 where you can see the memory leak with two restarts (11/8/17), the second is with v.383 which shows after as system restart (7:55pm 11/8/17) a much more stable memory usage taken (11/9/17). I will advise at my 24 hr uptime on my memory usage. Mike
                              Attached Files
                              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 Kerat View Post
                                I am on 3.0.0.382 about screen shows up for 1 Day 7 Hours 15 Minutes 27 Seconds.
                                Memory utilization is steady 76 Mbytes.
                                359 devices
                                180 events
                                3 scripts.

                                HS3 is Running on an RPI 3. Raspbian Jessie Lite with Mono version 3.12.


                                Sent from my iPhone using Tapatalk
                                Similar setup here except Raspbian Stretch Lite on Mono 5.2. Similar uptime too. Where have you pulled the memory usage from. Have you run Htop in a terminal session.

                                Comment

                                Working...
                                X