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 704387 - Removing bitshifts makes code slower
• Mozilla Bug 687127 - sqlite is slow on TI
• Mozilla Bug 681062 - dlmalloc is slow on SpiderMonkey
• Mozilla Bug 610296 - Code in a closure is slower.

node.js

• Node Issue 2476 - UglifyJS incorrectness in newer Node (intermittent failures in test_linespecific, and constant failures in speak.js)
• Node Issue 2280 - Creating large typed arrays crashes

Chrome/V8

• V8 issue 1822 - No .subarray or .set or ArrayBuffer
• V8 Issue 1630 - Compiled raytrace benchmark is very slow. Update: Looks like this is the case with most or all Emscripten benchmarks now.
• 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 10850 - LLVM 3.0 (svn) crashes on libc++ test.
• Bug 9893 - pvs.cpp from sauer fails in clang.

Closure Compiler

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

UglifyJS

• UglifyJS Issue 294 - Incorrectness with newer Node (see linked Node bug)