Wrote up a blog post describing a strange issue @AsafGartner and I ran into while building the post editor for the new website. Resolving it involved digging into both Chrome itself and the Go compiler, and it was really fun to pick apart. https://bvisness.me/chrome-wasm-crash/