No, we are not using that.
Regards,
Hitesh.
On Thursday, June 6, 2013 2:33:43 PM UTC+5:30, Vyacheslav Egorov wrote:
Do you report the size of your enormous Judy array to v8 via
AdjustAmountOfExternallyAllocatedMemory? If you do try disabling that.
Vyacheslav Egorov
On Jun 6, 2013 10:22
Are you frequently creating/slicing/toStringing any Buffers around a few MB?
This might be calling AdjustAmountOfExternallyAllocatedMemory indirectly.
Have you tried running without CollectAllAvailableGarbage and monitoring your
RAM usage after that?
Joran Greef
On 07 Jun 2013, at 12:07 PM,
Thank you at your inform.
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
v8-users group.
To unsubscribe from this group and stop receiving emails from it, send an email
Yeah, we serialize and deserialize a lot of data to/from Buffers. I
couldn't spot calls to AdjustAmountOfExternallyAllocatedMemory from
node_buffer though.
Haven't tried running without CollectAllAvailableGarbage. Did neutering
that disable only the last resort gc or entire garbage collection
Hi,
On Wed 05 Jun 2013 04:57, Bruno Jouhier bjouh...@gmail.com writes:
I'm playing with version 3.19 and generators and I would need a
JavaScript API to extract stack trace information from generators. I
don't really need the whole stacktrace but I would need at least
function name +
Hello, im trying to bind a download function but i get fatal error in api.h
line 549 CHECK(blocks_.length() == 0)
also my english is bad (sry)
my program goes like that
main thread call jsMainFunction
jsMainFunction
function jsMainFunction ()
{
_get(www.google.com,true,
function(data){
I think you are missing a handle scope:
void* fp = new std::functionvoid(void)(
[=]()
{
v::Locker locker(gIsolate);
v8::Isolate::Scope scope(gIsolate);
v8::HandleScope handle_scope(gIsolate);
std::vectorchar data = Download(url);
v::Handlev::Value arg =
Also, did you make sure that _all_ the code - including the code on main
thread - that you execute in gIsolate is protected by v8::Locker?
Hmm, i get my problem.
I made that class
class HandleScopeThreadSafety
{
v::HandleScope handleScope;
v::Locker locker;
public:
Well you should really create a locker *before* you create a HandleScope.
On Jun 7, 2013 6:47 PM, papi nokan...@gmail.com wrote:
Also, did you make sure that _all_ the code - including the code on main
thread - that you execute in gIsolate is protected by v8::Locker?
Hmm, i get my problem.
Hi Andy,
Thanks for your answer.
Of course, there is always only one frame (I should have thought of it)! So
what I need is precisely this frame: the function name would be a starter
(but there is not always one). The filename and line number would be a big
plus.
My little library implements
Ok strictly speaking, you should enter isolate *before* entering handle
scope. The proper order is:
- lock the locker
- enter isolate
- do any operations that access isolate
and creating a HandleScope is an operation that accesses isolate.
Hope this helps,
Dmitry
On Fri, Jun 7, 2013 at 6:59
11 matches
Mail list logo
