more G-Labs products

Author Topic: 100% CPU use by HomeGenie.exe after upgrade to 515  (Read 1901 times)

April 11, 2016, 09:58:41 PM
Read 1901 times

PeterM

  • *
  • Information
  • Newbie
  • Posts: 3
Upgraded to 515 and HomeGenie.exe is now using 100% CPU
My one C# program that was working fine before the upgrade now seems to be non-functional. No code changed and CPU usage stays the same even with that program disabled.

Any one have any ideas because at this rate I am going to ditch Home Genie and write something myself!

April 12, 2016, 04:40:07 PM
Reply #1

bkenobi

  • *****
  • Information
  • Global Moderator
  • Posts: 1525
Debugging a small bug is easier than writing your own interface IMO.

Are you running on Windows/Linux/RPi/etc?  Have you reviewed the mono output?  If you don't know how to read it, perhaps you could post it so someone could take a look.  You didn't provide any details on your configuration, so it seems like this post was mostly to complain rather than to get help.  If you provide details that could help resolve the problem, a constructive discussion could help get you going again.

April 12, 2016, 08:43:17 PM
Reply #2

PeterM

  • *
  • Information
  • Newbie
  • Posts: 3
Hardly a small bug when an automated upgrade renders a perfectly functional system unusable however ignoring the jibe... >:(

Running on Windows Server 2008 r2

With all programs disabled as soon as  HomeGenie.exe is started it goes to 100% CPU usage.

After the startup preamble the only log output is
2016-04-12 19:37:42.3338 Info HomeAutomation.HomeGenie.Automation   1006   Automation Program   Program.Status   Running
2016-04-12 19:37:42.3494 Info HomeAutomation.HomeGenie.Automation   1006   Automation Program   Program.Status   Idle
2016-04-12 19:37:43.2869 Info HomeAutomation.HomeGenie.Automation   1006   Automation Program   Program.Status   Running
2016-04-12 19:37:43.2869 Info HomeAutomation.HomeGenie.Automation   1006   Automation Program   Program.Status   Idle
2016-04-12 19:37:43.3338 Info HomeAutomation.HomeGenie.Automation   1006   Automation Program   Program.Status   Running
2016-04-12 19:37:43.3807 Info HomeAutomation.HomeGenie.Automation   1006   Automation Program   Program.Status   Idle

ad infinitum


April 12, 2016, 08:57:56 PM
Reply #3

bkenobi

  • *****
  • Information
  • Global Moderator
  • Posts: 1525
I'd try deleting program 1006.  I don't know what it is, but clearly it's running every 0.01-0.05 seconds.  I suspect there's an issue with it for one reason or another.  If that fixes the CPU usage, then the next step would be to figure out what happened to the script.  It should go without saying that having a backup of that script would be good for the next step.

April 12, 2016, 09:14:19 PM
Reply #4

PeterM

  • *
  • Information
  • Newbie
  • Posts: 3
Thank you for the suggestion. Is there an easy way to delete a program without using the web interface? At 100% CPU usage it all becomes a bit non-functional!

April 12, 2016, 10:48:00 PM
Reply #5

bkenobi

  • *****
  • Information
  • Global Moderator
  • Posts: 1525
By design, the web interface is how you would interact with HG.  However, you should be able to delete the script (stop HG first) if you navigate to the HG directory and delete the 1006.dll file.  I don't think HG will try to automatically recompile it, so you would then be able to access the web interface and modify/delete the program.  I'm curious what the program looks like as there was at least one other thread here that discussed a similar issue with a rogue program after update.  I believe they had some kind of statement in the code that was wrong and somehow HG was locking up when it looped through the code.

April 14, 2016, 05:57:19 AM
Reply #6

bkenobi

  • *****
  • Information
  • Global Moderator
  • Posts: 1525
FWIW, I just checked my HG setup and found that its running at 100% CPU usage as well.  I restarted the service and after a few minutes it was down to 2% as usual.  I don't know how long it was at the high usage, but I see that the log goes back to 4/8 and it was 100% at least that long.

April 14, 2016, 11:06:47 PM
Reply #7

petediscrete

  • ****
  • Information
  • Sr. Member
  • Posts: 220
Do you have any other platform to test rc515 on. Not too familiar with Windows after XP but do you have Windows 10 (I think that's what it's called). WS Server 2008  is two releases back from where it is now. Not sure what support service they give with it.

HG rc515 working well with Ubuntu 14.04 and of course working well with RPI platform I'm using now. I still feel there may have been some serious code rewrite between rc512 and rc515.

Would WS 2008 be overkill for HG. I must try Ubuntu SE and see how it performs.

December 04, 2016, 05:49:18 PM
Reply #8

jlpatte2

  • *
  • Information
  • Newbie
  • Posts: 2
Was any solution to this issue ever identified, I'm seeing 100% CPU usage on my copy of r525 running on Ubuntu 16.04. I have tried turning nearly everything off and it still seams to happen after a while. I haven't yet pulled any logs or anything, but will do so if I'm told its a set-up thing, and not a general known problem with the software.
Thanks, Josh

December 04, 2016, 08:32:45 PM
Reply #9

nolio

  • *****
  • Information
  • Global Moderator
  • Posts: 544
Is it the mono process ?
Did you try to reboot after desactivation of nearly all program ?

Do you have write your own script ? In case, yes, try to disable this one too ...

December 11, 2016, 04:38:01 PM
Reply #10

jlpatte2

  • *
  • Information
  • Newbie
  • Posts: 2
In case this helps someone else, it seems like it turned out to be the built in motion sensor stuff; I disabled or delete all of those programs and it has stopped spiking to 100%. Not sure why that stuff was so badly behaved since I have no motion sensors and hadn't touched any of that stuff in my install.

December 12, 2016, 05:00:25 PM
Reply #11

bkenobi

  • *****
  • Information
  • Global Moderator
  • Posts: 1525
You shouldn't have to delete the APP to get it to stop.  You should just be able to disable it.  In fact, I would guess that it was somehow misbehaving and simply stopping and starting it (or maybe a recompile thrown in there) would have fixed it.  Glad you figured it out and thanks for posting the solution.