Well, now I'm thoroughly confused. The v0.11rc3 version did not use readline() and it showed no memory growth. V.22 also does not use readline(), but it does show memory growth.
Either we're mistaken and 0.11rc3 does show memory growth, or something else besides readline() is causing it. -tk On Mon, Feb 25, 2019 at 6:07 AM Ralph Underwood <ralp...@gmail.com> wrote: > I haven't been using TOP to monitor memory usage - I have cmon running and > note the total memory use is creeping up. I restarted this station a > couple of times yesterday. I had a request to show the freezing level on > some charts - ended up setting soilTemp4 to 32 degrees and including it on > some charts. > > > [image: Screen Shot 2019-02-25 at 5.56.31 AM.png] > > > > Ralph > > > > On Sunday, February 24, 2019 at 6:34:05 PM UTC-8, Steve2Q wrote: >> >> My experience so far: >> >> With driver v 0.22, I first did a run of 44 hours with the DISABLE_ >> removed from the set time and get time portions of the driver. TOP showed >> 3.3% memory usage at startup, which climbed to 10.4% at 44 hours. >> >> I then replaced the DISABLE_ in both lines which put the driver back to >> its original state. Again there was 3.3% usage at startup, and while I am >> writing this, I have 9.1% after 36 hours. I am going to let in run in the >> current state to see if it levels off. >> >> Ralph, do you see the same thing happening? >> > -- > You received this message because you are subscribed to the Google Groups > "weewx-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to weewx-user+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
