I worked with tracemalloc some more... finally decided that it wasn't that I wasn't using tracemalloc right, it's that the leak isn't coming from python allocations. So I gave valgrind a try, and it flagged a leak that has a stack through SSL_SESSION_new. I'm pushing my weewx results through FTP and have TLS enabled... I temporarily disabled the requirement for TLS on the FTP server (pure-ftp), and disabled the weewx config to enable TLS, and it doesn't seem to be leaking memory now.
So... I guess the problem is in python's use of OpenSSL (at least from ftplib)... I figure if there was a leak in OpenSSL itself, across Fedora 35->Fedora 37, it would be more noticed. On Monday, November 28, 2022 at 7:04:17 PM UTC-6 vince wrote: > One last update - installed weewx and all the packages from rpms and I see > 'no' memory growth at all for the Simulator over f37 on a pi4. Same VSS > and RSS that weewx used when running pip-installed software in a python > venv. Unfortunately I can't duplicate your issue... > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/a6c5b713-7c98-486d-a4b1-f180da2b8963n%40googlegroups.com.
