Python itself is garbage collected, so it doesn't "leak" memory. Weewx is also pretty careful about avoiding circular references, which can slow down the GC process, leading to something that looks like an erratic slow leak.
So, when memory use grows without bounds, the problem is usually in some low-level library, probably written in C, that is misbehaving. If your problems started when you switched from the default font to a CentOS specific font, the problem is almost sure in some CentOS library that deals with your new font. There are a few Python tools to help you find a memory leak, but I have not found any of them very easy to use. Sorry, but this will take some careful sleuthing on your part. Try experimenting with different font types --- it may help you figure out which of the low-level libraries is the culprit. -tk On Sun, Aug 14, 2016 at 10:57 AM, Allan <[email protected]> wrote: > Den 07-07-2016 kl. 17:57 skrev Allan: > >> Den 07-07-2016 kl. 01:54 skrev Thomas Keffer: >> >>> Which Python graphics library are you using? PIL or Pillow? >>> >>> PIL has a known problem where it does not return font handles. There's a >>> workaround for this in weewx (since V2.6), but it's possible ByteWeather >>> tickles something else... >>> >>> If you're using PIL, give Pillow a try. >>> >> >> Python-pillow 2.0.0-19 seems to be installed here. >> I can't see anything with the name PIL. >> >> > Any ideas how trace this memleak ? > It is quite annoying, as it leaks 6GB ram/day > > BTW, the title is a bit misleading - this problem started > with Weewx v 3.0 > > > > Allan. > > > -- > 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. > -- 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.
