Here’s an informative story about and its experimental Wasm GC backend. In a dimly lit server room, a developer named Alex stared at a browser tab. Running Minecraft 1.12.2 — complete with Forge mods, redstone contraptions, and shaders — inside a vanilla browser. No plugins. No native code. Just JavaScript and WebAssembly.
The first test was a superflat world with 64 villagers. On the JS backend, frame rate dropped to 15 FPS with major GC spikes every 5 seconds. On Wasm GC? A steady 45 FPS. No visible hitches. The collector ran concurrently, reclaiming entire chunks of blocks and entity pathfinding data without stopping the world — in both senses. eaglercraft 1.12 wasm gc
Then came the experiment: .
This was Eaglercraft.
WebAssembly Garbage Collection is a new proposal that allows compiled languages (Java, C#, Kotlin) to manage memory using the browser’s built-in GC, rather than emulating it in JavaScript or manually managing linear memory. For Eaglercraft, this was revolutionary. Here’s an informative story about and its experimental