Ah, thanks a lot, that helped. It works now.

I wonder why it doesn't initializes such a standard allocator by default.

Also, the embedder guide should mention this. Are there maybe other things 
I need to init? I'm basically just doing 
this: https://developers.google.com/v8/get_started

Regards,
Albert


On Monday, March 10, 2014 10:28:46 AM UTC+1, Dmitry Lomov wrote:
>
> You still need to set the allocator, because V8 uses it internally, even 
> if you do not use ArrayBuffers in your code.
>
>
> On Mon, Mar 10, 2014 at 10:27 AM, Albert Zeyer 
> <[email protected]<javascript:>
> > wrote:
>
>> I'm not using ArrayBuffer in my code. I'm basically just using 
>> Script::Compile and Script::Run.
>>
>> It looks like a V8 issue...
>>
>>
>> On Monday, March 10, 2014 10:25:12 AM UTC+1, Dmitry Lomov wrote:
>>
>>> Ah, thought so. Read docs on v8::ArrayBuffer::Allocator. 
>>> (look at Shell::Main in d8.cc for an example)
>>>
>>> HTH,
>>> Dmitry
>>>  
>>>
>>> On Mon, Mar 10, 2014 at 10:20 AM, Albert Zeyer <[email protected]>wrote:
>>>
>>>> No, it's some own C++ app with V8. Some stripped down example C++ code 
>>>> is here: http://stackoverflow.com/questions/22294854/v8-fatal-error-
>>>> checkv8arraybufferallocator-null-failed
>>>>
>>>>
>>>> On Monday, March 10, 2014 10:17:23 AM UTC+1, Dmitry Lomov wrote:
>>>>
>>>>> How exactly do you run V8? Do you run d8?
>>>>>
>>>>> Dmitry
>>>>>
>>>>>
>>>>> On Mon, Mar 10, 2014 at 10:15 AM, Albert Zeyer 
>>>>> <[email protected]>wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I get this error when I try to run some JS code ([this](
>>>>>> http://pastebin.com/XesBSstJ) + [this](http://pastebin.com/0VawRb16)) 
>>>>>> with V8 (tried master from two weaks ago, 3.23.17, 3.24.40, 3.25.5):
>>>>>>
>>>>>>     #
>>>>>>     # Fatal error in ..\..\src\runtime.cc, line 785
>>>>>>     # CHECK(V8::ArrayBufferAllocator() != NULL) failed
>>>>>>     #
>>>>>>
>>>>>> A lot of other JS code has worked already, so I wonder what the 
>>>>>> problem is.
>>>>>>
>>>>>> It's on Win8 with a x64 build. V8 has been build just as described in 
>>>>>> the official docs (using gyp + MSVC 2012). I don't think that there was 
>>>>>> a 
>>>>>> problem because it worked fine already with most other JS code so far.
>>>>>>
>>>>>> I think that there might be an issue with V8 itself, but not sure...
>>>>>>
>>>>>> Some more information, including some C++ code:
>>>>>> http://stackoverflow.com/questions/22294854/v8-fatal-error-c
>>>>>> heckv8arraybufferallocator-null-failed
>>>>>>
>>>>>> Thanks,
>>>>>> Albert
>>>>>>
>>>>>>  -- 
>>>>>> -- 
>>>>>> v8-users mailing list
>>>>>> [email protected]
>>>>>>
>>>>>> 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 to [email protected].
>>>>>>
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>>  -- 
>>>> -- 
>>>> v8-users mailing list
>>>> [email protected]
>>>> 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 to [email protected].
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>  -- 
>> -- 
>> v8-users mailing list
>> [email protected] <javascript:>
>> 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 to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
-- 
v8-users mailing list
[email protected]
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 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to