r/javascript • • Jun 20 '16

Javascript developers, be warned about this crazy JIT bug in V8!

Last week I've spent a full day to fix very strange behavior in a single page application for my customer that only happens on Chrome 51 (maybe 52, but not in Canary 53).

After a while our SPA started behaving incorrectly...

It turned out to be a nasty bug in the V8 JIT engine.

Try the following in Chrome's developer console:

function foo() {
  return typeof null === "undefined";
}

for(var i=0; i<10000; ++i) console.log(foo())

This should of course always print false, but in Chrome 51, it prints true after about about 100 iterations (it varies...)

I want to warn other web-developers for this bug, to avoid many $$$ being wasted (or becoming insane ;-))

 

EDIT: The following - more realistic case that we had in third-party library code - will also fail, but after about 10 thousand iterations:

function isUndefined(thing){
    return typeof thing === "undefined";
}

for(var i=0; i<100000; i++) console.log(isUndefined(null));

 

EDIT: The bug also manifests itself with the more common pattern

typeof x !== "undefined"

UPDATE: I just tried this with the latest stable Chrome (52.0.2743.82), and it now works correctly :)

482 Upvotes

117 comments sorted by

View all comments

21

u/[deleted] Jun 20 '16

Trippy.

I get about 20% falses on the first time executing, then 100% true on consecutive executions on Windows x64 Chrome 51.

2

u/MCFRESH01 Jun 20 '16

Seems like it always has failures if you copy and paste the function and the loop at the same time. Works as expected if you past the function and then run the loop

0

u/[deleted] Jun 20 '16

[deleted]

1

u/repeatedly_once Jun 22 '16

I think it's because you're in the same thread when executing the JS. The first time it's executed is the first time the compiler has seen it after that is is associated null with undefined and does so ever more.