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 
Also confirmed it is restarting here as well. Wdisplay.ini shows 3:10:44 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.
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.
that’s good
that is what I observed here too
I changed a compiler directive that helped