Eaglercraft 1.12 Wasm Gc [work] -

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.

Eaglercraft had already pulled off the impossible: a full Java-to-JavaScript recompilation of the Minecraft client using TeaVM, plus a custom WebSocket-based multiplayer protocol. It ran in any modern browser, no installation needed. But version 1.12 was a beast — over 8 million lines of Minecraft code, plus the labyrinthine complexity of the 1.12.2 engine. Performance stuttered. Garbage collection froze the screen mid-PvP. eaglercraft 1.12 wasm gc

Then came the experiment: .

And the browser’s garbage collector just hummed along, quietly collecting fallen leaves in the background. WebAssembly Garbage Collection is a new proposal that

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. It ran in any modern browser, no installation needed

That night, the code was pushed to a public branch. Within days, players were running modded 1.12 worlds on school Chromebooks, fighting the Ender Dragon with zero lag spikes.

This was Eaglercraft.