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 [email protected]. For more options, visit https://groups.google.com/d/optout.
