External Issues

Emscripten issues in browser bug trackers

Emscripten is on the edge of what JavaScript engines are meant to do, so we often bump into JS engine bugs. This page links to issues in browser bug trackers that are related to Emscripten.

Firefox/SpiderMonkey

• Mozilla Bug 680951 - primes benchmark has regressed in speed.
• Mozilla Bug 678687 - ammo.js is slower with TI.
• Mozilla Bug 610296 - Code in a closure is slower.
• Mozilla Bug 610438 - Tracing does poorly on compiled Bullet.
• Mozilla Bug 610440 - Tracing heuristics do poorly on compiled Bullet.
• Mozilla Bug 612019 - Tracing typed arrays is fast, but combined with method JIT loses most of that.

Chrome/V8

• V8 Issue 1630 - Compiled raytrace benchmark is very slow.
• V8 Issue 1631 - Stack size limit too low for some CPython code.
• Chromium Issue 64600 - Bullet demo has many GC pauses.
• Chromium Issue 84521 - Doom demo crashes.

Opera

• The CPython demo and others do not run due to a bug in Opera's JS engine. Opera has been informed, but does not have a public bug tracker to link to.

LLVM

• Bug 9893 - pvs.cpp from sauer fails in clang.
• Bug 9894 - rendermodel.cpp from sauer fails in clang.

Closure Compiler

• Closure Compiler Issue 492 - Emscriptened CPython hits a hardcoded iteration limit during Closure analysis.
• Closure Compiler Issue 534 - OutOfMemoryError on LLVM-optimized ammo.js.