The developer of GoOS is addressing memory management and garbage collection challenges in the upcoming 0.2.8 release. Since the operating system is built using TinyGo without the standard Go runtime, the system lacks built-in support for dynamic memory allocation and automatic garbage collection.
Previously, the kernel utilized a leaking garbage collector configuration, which only supported memory allocation. To maintain stability, the kernel architecture prohibits dynamic allocations in repetitive paths, relying instead on pre-allocated objects, object reuse, and specialized memory pools.
The userspace environment previously relied on a basic bump allocator for memory management. In this setup, functions for freeing memory and garbage collection were non-functional placeholders. The new release aims to replace these limitations with a functional heap and garbage collector.
