Freaky heisenbug where intersects is falsely negative after many events, Chrome only

[gkop]

In Chrome 35 and Chromium 35, consistently, after a hundred or so (varies) mouseover/mouseout combos, intersects seems to come back negative when it should not.

It's inside this conditional - https://github.com/jeromeetienne/threex.domevents/blob/master/threex.domevents.js#L268

If I put a console.log inside this conditional, after this bug manifests, that console.log line is never reached.

However if I set an inspector breakpoint at the line with the console.log, the breakpoint trips with the next event.

The bug manifests with developer tools open or closed, with Three.js r59 and r67.

Meanwhile I cannot replicate the bug in Iceweasel 24.6.0.

[jeromeetienne]

thanks for reporting. how can i easily reproduce the bug ?

i use it on many time without issue

[gkop]

I will extract a minimum test case when I have time. I cannot reproduce in your demos.

[micmmakarov]

I fix this bug by calculating offset in Jquery https://github.com/micmmakarov/threex.domevents