Re: [JS-internals] Weak references

2013-11-04 Thread Brendan Eich
Terrence Cole wrote: Recently, Luke tried turning down the incremental slice time knob to see how low we could go. He found that2ms is easily doable, except when traversing the browser C++ heap, taking about6ms. I wonder how this scales on, say, a Nexus 4 (not to drag us all down to a ZTE Ope

Re: [JS-internals] Weak references

2013-11-04 Thread Terrence Cole
On 11/02/2013 02:59 PM, Brendan Eich wrote: > David Bruant wrote: >> Article version and longer talk at >> http://www.html5rocks.com/en/tutorials/memory/effectivemanagement/ > > Thanks. > >>> They showed historical plots revealing gmail bugs, V8 GC regressions, >>> all the interesting dirt. Their

Re: [JS-internals] Weak references

2013-11-04 Thread Terrence Cole
On 11/02/2013 10:24 AM, Allen Wirfs-Brock wrote: > > On Nov 1, 2013, at 3:17 PM, Jason Orendorff wrote: > >> On 11/1/13 1:52 PM, David Bruant wrote: >>> In any case, I've stopped being against weakrefs after a message by >>> Mark Miller[...] >> I am now going to try to convince you that you shoul

Re: [JS-internals] Weak references

2013-11-04 Thread Terrence Cole
On 11/03/2013 08:16 AM, Brendan Eich wrote: > Bobby Holley wrote: >> This won't solve esoteric cross-vat use cases, but I think it would be a >> nice way to bulldoze the subtle gotchas that make it so easy to introduce >> subtle leaks in large-scale JS. > > With an MVC framework, nukeSandbox is of

Re: [JS-internals] Weak references

2013-11-04 Thread Brendan Eich
Bobby Holley wrote: On Sun, Nov 3, 2013 at 1:50 PM, David Bruant wrote: > hueyfix-style tools for client code or implementors? > Client code will have one in ES6 in the form of revocable proxies. Initial > post on the topic (mentioning GC specifically) [1] and API [2] (also > available in

Re: [JS-internals] Weak references

2013-11-04 Thread Bobby Holley
On Sun, Nov 3, 2013 at 1:50 PM, David Bruant wrote: > hueyfix-style tools for client code or implementors? > Client code will have one in ES6 in the form of revocable proxies. Initial > post on the topic (mentioning GC specifically) [1] and API [2] (also > available in the latest ES6 draft). > Y

Re: [JS-internals] Browser sluggishness due to GetElementIC, TypeMonitorResult, Shape::search, and others

2013-11-04 Thread Nicholas Nethercote
On Mon, Nov 4, 2013 at 12:19 AM, Brendan Eich wrote: > How about bisecting, if the symptom is observable in a few minutes of > running a nightly? It's not that reliable, unfortunately. I'll try profiling, as Kannan suggest. Nick ___ dev-tech-js-engine

Re: [JS-internals] Browser sluggishness due to GetElementIC, TypeMonitorResult, Shape::search, and others

2013-11-04 Thread Brendan Eich
How about bisecting, if the symptom is observable in a few minutes of running a nightly? /be Kannan Vijayan November 3, 2013 9:50 PM You're hitting slowpath named property accesses (JSOP_GETELEM style) which are going through an Ion IC, but which are not getting