Hi, Allen

Your conclusions do not surprise me. This is not the first memory leak we
have found in the underlying operating system. Usually we can work around
the leaks by caching... something.

Right now, weewx uses a cache for TrueType fonts. Which font is causing the
problems?

-tk

On Fri, Sep 9, 2016 at 2:46 PM, Allan <[email protected]> wrote:

> Hi Thomas...
>
> I tried the 2 files - it didn't change anything.
>
> That made me think, I'd better try testing this from scratch, so I
> installed a new Centos 7 in a VM, and installed weewx 2.7 there.
> As usual, with no changes, there are no leaks; but as soon as I fixed the
> font paths, it leaks just as much as my 3.x builds :-/
>
> Sorry, I was sure, this started with 3.0 - but I must have noticed the
> wrong font paths at the same time as the upgrade.
>
> To have something to compare, I have a Fedora 25 Alpha VM in test here, so
> I just tried to install latest weewx to that system.
>
> The 2 VM's have been running for 40 mins right now. F25 uses 35MB C7 uses
> 76MB for weewx(python) process ( and for the real station on the C7 host,
> it now uses 4.2GB ram after 23h run (it is restartet every 24h)
>
> It sure looks like a problem with Centos 7 - but I have no clue, what to
> do about it.
>
>   Allan.
>
>
> Den 06-09-2016 kl. 03:54 skrev Thomas Keffer:
>
>> The only thing that changed in the plotting functions between V2.7 and
>> V3.5 is that the plot labels now uniformly use Unicode. Before it was a
>> mishmash.
>>
>> The two commits of weeplot that introduced this were done on 20 Feb
>> 2016. You could use the last commit
>> (b1594a81838349fd9d8994c80ade8fc456083385
>> <https://github.com/weewx/weewx/tree/b1594a81838349fd9d8994c
>> 80ade8fc456083385/bin/weeplot>) before
>> this and see if it does not leak.
>>
>> Replace weeplot/genplot.py with this version
>> <https://raw.githubusercontent.com/weewx/weewx/b1594a8183834
>> 9fd9d8994c80ade8fc456083385/bin/weeplot/genplot.py>.
>> Replace weeplot/utilities.py with this version
>> <https://raw.githubusercontent.com/weewx/weewx/b1594a8183834
>> 9fd9d8994c80ade8fc456083385/bin/weeplot/utilities.py>.
>>
>> See what that does.
>>
>> -tk
>>
>>
>>
>> On Mon, Sep 5, 2016 at 3:24 PM, Allan <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>     Sorry it took a few more days to test it ;-)
>>
>>     Running Weewx with Centos 7 in VirtualBox with standard skin,
>>     and simulator 'station' does not leak - but the font paths
>>     in the skin are wrong for Centos.
>>     After fixing the font paths, and setting archive interval to 60
>>     (to speed it up) - it leaks 1GB mem/day.
>>
>>     So we can eleminate ByteWeather here as the problem - it is the font
>>     loading system, that leaks.
>>
>>     Again, it worked with Weewx 2.7
>>
>>
>>        Allan.
>>
>>
>>
>>     Den 20-08-2016 kl. 01:17 skrev Thomas Keffer:
>>
>>         If you can find a reproducible problem in the standard skin,
>>         that would
>>         get my attention. :-)
>>
>>         -tk
>>
>>         On Fri, Aug 19, 2016 at 3:48 PM, Allan
>>         <[email protected]
>>         <mailto:[email protected]>
>>         <mailto:[email protected]
>>         <mailto:[email protected]>>> wrote:
>>
>>              Den 20-08-2016 kl. 00:37 skrev Thomas Keffer:
>>
>>                  Hello, Allan
>>
>>                  Do you get a memory leak if you use the standard skin?
>>
>>
>>              Heh, don't really know - haven't tried that for a long time
>> :-)
>>
>>              I guess I can try that out in the simulator VM - but it'll
>>         take a
>>              day or 2
>>
>>
>>                 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]
>>         <mailto:weewx-user%[email protected]>
>>              <mailto:weewx-user%[email protected]
>>         <mailto:weewx-user%[email protected]>>.
>>              For more options, visit https://groups.google.com/d/optout
>>         <https://groups.google.com/d/optout>
>>              <https://groups.google.com/d/optout
>>         <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]
>>         <mailto:weewx-user%[email protected]>
>>         <mailto:[email protected]
>>         <mailto:weewx-user%[email protected]>>.
>>         For more options, visit https://groups.google.com/d/optout
>>         <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]
>>     <mailto:weewx-user%[email protected]>.
>>     For more options, visit https://groups.google.com/d/optout
>>     <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]
>> <mailto:[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.
>

-- 
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.

Reply via email to