Gary,

You are right, one graph was enough to trigger the memory grow! The strange 
thing tonight was an huge increase in memory for about one hour (200kB) 
followed by the ‘normal’ grow without any clue what happened in de syslog.

Luc

On Sunday, 29 March 2020 22:55:40 UTC-3, gjr80 wrote:
>
> So maybe one of those updated modules is the problem. Running with one 
> plot still calls PIL so if PIL is the leak it will still show. As Vince 
> said you really need to work systematically to find the culprit. PIL seemed 
> to be low hanging fruit to me.
>
> Gary
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/6fca91bd-5abe-428a-9265-329a6ca63cf2%40googlegroups.com.

Reply via email to