[v8-users] Re: V8 5.2 appears to be 3x slower than V8 3.27 when running for loops

I should add... this performance drop is only seen when running on an Android Wear watch (1.1 Ghz, clocked down to even further). On a phone or desktop you'll see 60 fps in both V8 5.2 and 3.27, it's only when you drop into the sub 1Ghz range that you see the steep drop in V8 5.2 (3.27 still

[v8-users] V8 5.2 appears to be 3x slower than V8 3.27 when running for loops

We have a UI prototyping tool for Android that uses V8 under the hood. Recently we upgraded from V8 3.27.34.4 to V8 5.2 (so we could get es2015 support) but now the frame rate when dragging a single object on the screen has dropped from 60 fps to 20 fps (running the exact same JavaScript code).

[v8-users] ScriptCompiler::CompileFunctionInContext creates negative offsets in the ScriptOrigin data structure that breaks debugging

Then, when chrome sees a negative offset in the data it gets in the chrome debugging prototocol data, it seems to just ignore the script.. so I have to crate my ScriptOrigin object with a bogus offset in order to get the number to be positive (but not too positive) because it also seems to