Following up with final results from the fleet test of the 3.13.5-2+deb13u4 test build, as promised.
The test build has now run for about 21 hours (installed midday 2026-07-16, all hosts rebooted) on 7 production weewxd instances across 7 Raspberry Pi 5 machines (arm64, trixie). Each instance runs an explicit gc.collect() every 3 hours, so the fleet has accumulated: 49 consecutive clean GC passes, 0 crashes, 0 core dumps. Largest collection per host (objects collected in a single pass): bambi5t 60886 judygirldog5t 58153 cosmo5t 49817 ella5t 44104 mrpojangles5t 40008 judy5t 36825 charlemagne5t 28475 For comparison, under deb13u3 this same fleet crashed 4 times in roughly 130 passes (~3% per pass), and every fatal pass had collected at least ~22.9k objects. On deb13u4, every one of the 7 hosts has now completed at least one pass larger than the smallest collection that crashed deb13u3, including several far beyond the deb13u3 range, all clean. As far as this fleet can tell, deb13u4 fully resolves the issue. Thanks for the quick turnaround on the fix, and glad to see it accepted into proposed-updates. John Kline
