cloudy cloudy

Author Topic: Memory requirements for 64bit gui  (Read 1320 times)

0 Members and 1 Guest are viewing this topic.

Offline brianf7408

  • Posts: 69
  • OS/Browser:
  • iOS 11.2.1
  • Safari 11.0
Re: Memory requirements for 64bit gui
« Reply #15 on: December 27, 2017, 04:50:06 PM »
Thanks for the instruction grantk.  Yes i had previously figured out the start at reboot with sudo.

Offline Weather Display

  • Posts: 85,438
  • Davis VP2
  • New Zealand
  • OS/Browser:
  • Win NT 10.0
  • Chrome 63.0.3239.84
    • Weather Display
Re: Memory requirements for 64bit gui
« Reply #16 on: December 27, 2017, 05:49:26 PM »
I would think it would be better if I get WD to restart itself daily instead

Offline brianf7408

  • Posts: 69
  • OS/Browser:
  • iOS 11.2.1
  • Safari 11.0
Re: Memory requirements for 64bit gui
« Reply #17 on: December 27, 2017, 06:13:52 PM »
That would be cool!

Offline Weather Display

  • Posts: 85,438
  • Davis VP2
  • New Zealand
  • OS/Browser:
  • Win NT 10.0
  • Chrome 63.0.3239.84
    • Weather Display
Re: Memory requirements for 64bit gui
« Reply #18 on: December 27, 2017, 07:14:41 PM »
have done that now
latest update
tested and works at 3:10:30 am

Offline GrantK

  • Posts: 215
  • Davis VP2+ with 24 Hr SPFARS
  • Bay of Islands, New Zealand
  • OS/Browser:
  • Win NT 10.0
  • Chrome 63.0.3239.84
Re: Memory requirements for 64bit gui
« Reply #19 on: December 27, 2017, 08:51:39 PM »
Thanks Brian for tidying that up.

I noticed there is another executable called WDstartdelay present in the .tar file so have copied that into wdisplay along with the main executable.  I've left it running and will check on it tomorrow morning to make sure the restart has taken place.  If not I can revert to the previous method.

Offline GrantK

  • Posts: 215
  • Davis VP2+ with 24 Hr SPFARS
  • Bay of Islands, New Zealand
  • OS/Browser:
  • Win NT 10.0
  • Chrome 63.0.3239.84
Re: Memory requirements for 64bit gui
« Reply #20 on: December 28, 2017, 05:04:28 PM »
have done that now
latest update
tested and works at 3:10:30 am
Confirmed.

WDISPLAY.INI records the startup time as 3:10:43 so I guess the intervening 13 seconds are the time taken to reload WD and get things running again, which seems reasonable.  Memory and CPU usage have returned to normal after the restart.

I am about to go away for 4 days but will keep an eye on things from afar.  With this new restart arrangement I can hopefully rely on WD to run like clockwork in the way Linux does  :wink:

Offline brianf7408

  • Posts: 69
  • OS/Browser:
  • iOS 11.2.1
  • Safari 11.0
Re: Memory requirements for 64bit gui
« Reply #21 on: December 29, 2017, 12:39:48 PM »
Also confirmed it is restarting here as well. Wdisplay.ini shows 3:10:44 am.

Offline Weather Display

  • Posts: 85,438
  • Davis VP2
  • New Zealand
  • OS/Browser:
  • Win NT 10.0
  • Chrome 64.0.3282.140
    • Weather Display
Re: Memory requirements for 64bit gui
« Reply #22 on: February 08, 2018, 08:24:57 AM »
see if this update has it where the memory leak is a bit better?
http://www.weather-display.org/downloadfiles/weatherdisplay.tar.gz

I suspect the problem is with the compiler uses ARC (automatic reference counting)

Offline GrantK

  • Posts: 215
  • Davis VP2+ with 24 Hr SPFARS
  • Bay of Islands, New Zealand
  • OS/Browser:
  • Win NT 10.0
  • Firefox 58.0
Re: Memory requirements for 64bit gui
« Reply #23 on: February 08, 2018, 09:20:40 AM »
see if this update has it where the memory leak is a bit better?
http://www.weather-display.org/downloadfiles/weatherdisplay.tar.gz

I suspect the problem is with the compiler uses ARC (automatic reference counting)
Thanks Brian, I've installed the new executable now and will keep an eye on it.

Offline GrantK

  • Posts: 215
  • Davis VP2+ with 24 Hr SPFARS
  • Bay of Islands, New Zealand
  • OS/Browser:
  • Win NT 10.0
  • Firefox 58.0
Re: Memory requirements for 64bit gui
« Reply #24 on: February 08, 2018, 07:18:46 PM »
see if this update has it where the memory leak is a bit better?
http://www.weather-display.org/downloadfiles/weatherdisplay.tar.gz

I suspect the problem is with the compiler uses ARC (automatic reference counting)
From what I've seen so far, it looks like this problem has been pretty much solved.  Memory usage is still well under 1GB after 5 hours operation and looks to be increasing only very slowly.  I'll have another look late tonight and report back, but this is a huge improvement!

Many thanks Brian.

Offline Weather Display

  • Posts: 85,438
  • Davis VP2
  • New Zealand
  • OS/Browser:
  • Win NT 10.0
  • Chrome 64.0.3282.140
    • Weather Display
Re: Memory requirements for 64bit gui
« Reply #25 on: February 08, 2018, 07:30:15 PM »
that's good
that is what I observed here too
I changed a compiler directive that helped

 

cumulus