Oh, a couple other things: When did you upgrade to V3.0?
The interface to search list extensions changed between 2.7 and 3.0. Did whoever publishes Byteweather use search list extensions? Did their code change? Did they use any additional low-level routines in their extension? I don't mean to pass the buck, but I'm sure you can appreciate that we can't support every 3rd party skin out there. The base weewx does not have any memory problems on Debian. My own station has runs for months with stable memory usage. Not so sure about CentOS, but, at this point, you're the only one who has reported a problem (so far). -tk On Fri, Aug 19, 2016 at 3:37 PM, Thomas Keffer <tkef...@gmail.com> wrote: > Hello, Allan > > Do you get a memory leak if you use the standard skin? > > -tk > > On Fri, Aug 19, 2016 at 3:28 PM, Allan <weewx2...@warpspeed.dyndns.dk> > wrote: > >> Hi Thomas... >> >> Den 19-08-2016 kl. 03:19 skrev Thomas Keffer: >> >>> 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. >>> >> >> No, the problem started, when I switched from Weewx 2.7.x to 3.0 >> The only reason I know it is font related, is because i created a virtual >> PC with same OS and same byteweather theme with weewx in simulator mode - >> just to see, if it was any of my mods. It didn't leak; but I forgot fixing >> the font paths used in the theme (i uses debian paths - on Centos, they are >> slightly different). >> >> After I fixed the font paths, it was leaking, just as my real system. >> >> 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. >>> >> >> First of all, I'm pretty new to linux, so that will not be easy :-) >> Then again - this didn't happen in same config with WeeWx 2.7 , it >> started the second I updated to V3.0 >> >> As mentioned earlier, I reproduced this in a VM , running same Centos 7 >> and same Weewx and Byteweather theme running simulator - where the only >> thing I changed was the font path i byteweather theme. >> >> If you are a master of debugging this,(:-)) I can easily give you access >> to this VM (SSH/VNC or whatever), in case you do not want to setup such an >> equal env. >> >> >> >> 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 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.
