Constantly needing to create a LocalT::New() every time I need to use a
PersistentT in cases like the above isn't playing nicely. I've noticed
since the change that GC time from --prof has grown around 5% in high I/O
scenarios.
It really shouldn't change GC times whatsoever. I did
On Wed, Jul 24, 2013 at 3:34 PM, Dan Carney dcar...@chromium.org wrote:
Constantly needing to create a LocalT::New() every time I need to use a
PersistentT in cases like the above isn't playing nicely. I've noticed
since the change that GC time from --prof has grown around 5% in high I/O
The issue Trevor's reporting is that each Local that's created with
LocalT::New() gets added to the active HandleScope's internal list.
Before the Persistent changes, dereferencing a Persistent was cheap,
now it's not (if it's weak.)
That still shouldn't affect GC times very much,
In v8 i have handle
HandleValue number1 = NumberObject::New(100);
What properties I must add if I want number1 was accessible from JS code.
In this way js code can change it:
number1=number1+1;
Now in v8 number1 is also 101.
--
--
v8-users mailing list
v8-users@googlegroups.com
Ok. Thank you
Pada 25 Jul 2013 03:46, jk j.kutrzeb...@wp.pl menulis:
In v8 i have handle
HandleValue number1 = NumberObject::New(100);
What properties I must add if I want number1 was accessible from JS code.
In this way js code can change it:
number1=number1+1;
Now in v8 number1 is
