Announcement

Collapse
No announcement yet.

Out of Memory. Crashing HS3 - Solution!

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

  • Out of Memory. Crashing HS3 - Solution!

    I purchased this app and through a long process of elimination of other plug ins I have found that the Nest plug in crashing my system 1-2 times daily. It becomes totally unresponsive. It gives an out of memory error. It was so bad I turned the plug in off and now everything works flawlessly. I really want this plug in to work since I have a large Nest collection, 2 thermometers, 3 Protects, and 4 cameras. Anyone have any suggestions? Are there too many Nest devices on my network?

  • #2
    the number of devices should not be a problem

    On what OS are running HS3? How much memory do you have on this machine?

    Can you try to monitor how much memory the HSPI_Nest.exe process takes, and when does it increase?

    Do you have any error in the logs, except the out of memory one?

    Comment


    • #3
      I'm running on Linux. The homeseer SEL. The guys at Homeseer remotely logged in and stated the couldn't see any memory issues. Is there a plug in to monitor memory issues? Most of the time it doesn't even give an error. I just know that Homeseer runs fine with the plug in turned off and as soon as I try using again it crashes randomly and intermittently. Most of the time with no errors in the log

      Comment


      • #4
        Originally posted by smashburn View Post
        I'm running on Linux. The homeseer SEL. The guys at Homeseer remotely logged in and stated the couldn't see any memory issues. Is there a plug in to monitor memory issues? Most of the time it doesn't even give an error. I just know that Homeseer runs fine with the plug in turned off and as soon as I try using again it crashes randomly and intermittently. Most of the time with no errors in the log
        I don't think there is a plugin that does that. You could follow the steps advised by Pete in this thread: https://forums.homeseer.com/showthread.php?t=192512

        When you enable the Nest plugin, does it work as expected before HS3 crashes?

        Comment


        • #5
          Yes. It runs great for a few hours but then it unexpectedly locks up the whole system.

          Comment


          • #6
            Looking back in the forums it seems more and more people are having this issue. Hope we find a fix soon.

            Comment


            • #7
              could you try to only enable the Nest plugin, use the htop command to monitor the mono processes, and take a screenshot before it crashes, so that we can confirm that the problem is the Nest plugin using a lot of memory.

              thanks

              Comment


              • #8
                I have the same issues, on an out-of-the-box SEL Pro. I only see the HSConsole process to use more and more CPU. RAM use is also creeping up from < 400 MB. HS Support tipped me off. I disabled Nest plugin and will report back. It typically took about 12 hours for mono to crash. HSConsole would lock-up before it crashes.
                Attached Files
                Last edited by sbrunner; December 18th, 2017, 09:31 PM.

                Comment


                • #9
                  Appears to be really the Nest plugin causing the race condition. I am suspecting that this is not actually the plugin itself, but how HS3 reacts to it.

                  htop attached form this morning after running for 15 hours. HS3 typically crashed after about 12 hours.
                  Attached Files

                  Comment


                  • #10
                    @spud, if you want we can troubleshoot after xmas. I can give you SSH access.

                    Comment


                    • #11
                      I have the Nest plugin running here on an SEL with HS3 build 398. What do I have to do to see the issue that is reported?
                      website | buy now | support | youtube

                      Comment


                      • #12
                        I see the CPU occasionally rising to about 60%, but it only stays there for 10 seconds or so, then goes back down. I assume it might just be the plugin updating. So far that is all I see and memory is steady. If someone has a procedure or configuration that shows the reported issue, let me know.
                        website | buy now | support | youtube

                        Comment


                        • #13
                          Originally posted by rjh View Post
                          I see the CPU occasionally rising to about 60%, but it only stays there for 10 seconds or so, then goes back down. I assume it might just be the plugin updating. So far that is all I see and memory is steady. If someone has a procedure or configuration that shows the reported issue, let me know.
                          Spud just sent me this way, I've been battling this for the last week until he sent me this thread. On my Odroid XU4, the HS3 process normally idles at 8-30%, but it will spike and stick at 160%+, and if I leave it alone, spike to 350%+, until the system eventually overheats and shuts off. I have reproduced this reliably all week since I moved from Windows to Linux. It can take anywhere from a few minutes to a few hours with the Nest Plugin enabled.

                          System:
                          • Odroid XU4
                          • Ubuntu 17.10 ARM
                          • Mono 5.4.1.6 (tarball Wed Nov 8 21:23:55 UTC 2017) (installed via apt repo)
                          • Observed on HS3 versions .368 and .398
                          • Nest Plugin version 3.0.0.28


                          I am willing to try whatever debugging you need.

                          Comment


                          • #14

                            Comment


                            • #15
                              Originally posted by tome10 View Post
                              I had issues with my Denon Plugin after first setting it up last year, it ended up being that I enabled detailed logging, and it quickly consumed 16 gigs or whatever I had left on my hometroller. I don’t know if this Plugin has this detailed logging or whatever, but maybe that would be something to check.
                              I'm not sure this is the case. If it's logging at debug, I don't see where. Also looks like it's set to Info in the Plugin Config.

                              Comment

                              Working...
                              X