github-actions
released this
20 Nov 20:22
·
708 commits
to master
since this release
What's Changed
The most critical fix in this LTS release is the goroutine leak. If a device is operating in a network where the DHCP server provides more than one DNS server address (or the device is configured to have a static/manual network with more than one DNS server), then there is a slow leak of goroutines inside the zedbox process which will lead to running out of memory and an OOM crash. In some environments and configurations we've seen that as often as one day.
There are also important memory garbage collection fixes to make sure the golang GC kicks in fast enough when there is a burst of memory allocations.
- [12.0 stable] Enhance LinuxCollector to support detecting multiple app VIF IPs by @milan-zededa in #4256
- [12.0-stable] pillar/assignableadapters: clear error strings by @christoph-zededa in #4240
- [12.0-stable] mkimage-raw-efi: Find persist partition when installing into another disk by @rene in #4283
- [12.0 stable] Properly initialize AppNetworkStatus after invalid config was fixed by @milan-zededa in #4285
- [12.0-stable] Configure Go GC based on pillar memory limit or global config by @rouming in #4275
- [12.0-stable] pkg/pillar: make ioBundleError deepcopy-able by @christoph-zededa in #4302
- [12.0-stable] pillar: Use hard memory limit for EVE memory management. by @OhmSpectator in #4306
- [12.0-stable] zedbox: force GC on cgroups memory pressure events by @rouming in #4309
- [12.0-stable] Allow EVE memory limits above 4GB. by @OhmSpectator in #4313
- [12.0-stable] eve labelling and assets fix by @yash-zededa in #4418
- [12.0-stable] liburing source update by @shjala in #4427
- [12.0-stable] pillar/devicenetwork: fix goroutine leak by @christoph-zededa in #4424
Full Changelog: 12.0.4-lts...12.0.5-lts