Re: [v8-users] Arraybuffer

2018-09-13 Thread Peter Schow
On Thu, Sep 13, 2018 at 10:45 AM dan Med  wrote:
> That isn’t my question
> Arraybufferbuilder:append how could I get that to be called.
> What I really need is a little guidance on how to understand how v8 will 
> parse my JavaScript script and how it will allocate the data.
> Maybe even how a buffer or if there’s something that describes how buffers 
> are handeled or if there’s a file or code that tells me that not the memory I 
> know... just how it will execute it that’s all

Starting with the sample REPL code at:
 https://github.com/v8/v8/blob/master/samples/shell.cc

could answer your questions.  In the days that you've been pursuing
this, you could have traced all this by now.  Good luck.

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [v8-users] Arraybuffer

2018-09-13 Thread dan Med
That isn’t my question
Arraybufferbuilder:append how could I get that to be called.
What I really need is a little guidance on how to understand how v8 will
parse my JavaScript script and how it will allocate the data.
Maybe even how a buffer or if there’s something that describes how buffers
are handeled or if there’s a file or code that tells me that not the memory
I know... just how it will execute it that’s all

On Thu, 13 Sep 2018 at 18:42, J Decker  wrote:

>
>
> On Thu, Sep 13, 2018 at 9:21 AM dan Med  wrote:
>
>> Still no one ?
>>
> I dont know how I could have been more clear about the memory.
> https://groups.google.com/d/msg/v8-users/MNpTNiRaBmM/Muz5-KHpBgAJ
>
> Why do you think there is some magic to the buffer of an arraybuffer?
> It's just continuous bytes in memory.  Especially well suited for
> communicating arrays of data to WebGL.
>
>
>> On Thu, 13 Sep 2018 at 16:31, dan Med  wrote:
>>
>>> Okay I will but, how could I be sure when blink on the renderer process
>>> executes arraybufferbuilder ??
>>> Or one more thing, can u redirect me to checkout how v8 represents data
>>> in memory, how would it handle arraybuffers?
>>> The only thing I’ve managed to find ( in the github repo ) was a
>>> JavaScript file which contained if I remember correctly, 2 definitions of
>>> sorting algorithms.
>>>
>>> On Thu, 13 Sep 2018 at 16:23, @soylentgraham 
>>> wrote:
>>>
 You seem to be purposely ignoring the responses to your questions.

 If you still want help, build v8, build a program, breakpoint the
 function you want to see is called, debug it (this alone answers all your
 questions), then come back if you still have a VERY SPECIFIC question.


 On Thursday, 13 September 2018 15:15:03 UTC+1, dan Med wrote:
>
> No one is willingly to help me  ?
>
> On Wed, 12 Sep 2018 at 20:34, dan Med  wrote:
>
>> Yeah i meant   ArrayBuffer*Builder*::Append my bad but when it
>> is actually called in blink ?
>> Cause by the name it has to do with Arraybuffers..
>> Plus if i build v8 so i can examine the memory layout, where is the
>> code on how v8 handeles arraybuffer ?
>> Where is the doc or some source where there's explained how v8
>> represents object in memory, how can i be sure that in memory i'm not
>> starrying at a pointer instead of an object or something like that...
>>
>> Il giorno mer 12 set 2018 alle ore 19:40 Jakob Kummerow <
>> jkum...@chromium.org> ha scritto:
>>
>>> On Wed, 12 Sep 2018 at 13:15, dan Med  wrote:
>>>
 But can someone help me understand the arraybuffer part ? How to
 call arraybuffer::append and when I create an instance of a 
 arraybuffer it
 will create it with maximum size so 37... bytes and will only say that 
 the
 bytes used are the one which I’ve declared ?

>>>
>>> There is no ArrayBuffer::Append. Read closely: you've found
>>> ArrayBuffer*Builder*::Append, which is some implementation detail
>>> in Blink (not V8). I don't know when it's called, but I've pointed out
>>> before how you can find out. When you use ArrayBuffer objects in
>>> JavaScript, then that code is not executed at all.
>>>
>>> And when you create an ArrayBuffer(10) in JavaScript, it definitely
>>> does not allocate 32KB of memory. It'll round up to the nearest 
>>> multiple of
>>> a pointer size.
>>>
>>> On Wed, Sep 12, 2018 at 10:09 AM dan Med 
>>> wrote:
>>>
 Oh one more thing, so each tab in chrome is handeled as a single
 process, but Is the same process sandboxes with the Windows 10 kernel.
 Security or there’s another process which is sandboxes and then the 
 main
 tab process the ( renderer ) is executed inside of it ?

>>>
>>> That's a completely unrelated question which has nothing to do with
>>> V8 and does not belong in this thread. I suggest to look around on
>>> http://dev.chromium.org/developers for a bunch of things that have
>>> been explained before.
>>>
>>> On Wed, 12 Sep 2018 at 00:12, Peter Schow  wrote:
>
>> On Tue, Sep 11, 2018 at 2:09 PM dan Med 
>> wrote:
>> >
>> > Would you suggest to build v8 such that I can debug it as I
>> want ?
>>
>> It's difficult to go wrong with this approach if you want to
>> better
>> understand V8 or any large, complex system.
>>
>> --
>> --
>> v8-users mailing list
>> v8-u...@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 to v8-users+u...@googlegroups.com.
>> For more options, 

Re: [v8-users] Arraybuffer

2018-09-13 Thread J Decker
On Thu, Sep 13, 2018 at 9:21 AM dan Med  wrote:

> Still no one ?
>
I dont know how I could have been more clear about the memory.
https://groups.google.com/d/msg/v8-users/MNpTNiRaBmM/Muz5-KHpBgAJ

Why do you think there is some magic to the buffer of an arraybuffer?  It's
just continuous bytes in memory.  Especially well suited for communicating
arrays of data to WebGL.


> On Thu, 13 Sep 2018 at 16:31, dan Med  wrote:
>
>> Okay I will but, how could I be sure when blink on the renderer process
>> executes arraybufferbuilder ??
>> Or one more thing, can u redirect me to checkout how v8 represents data
>> in memory, how would it handle arraybuffers?
>> The only thing I’ve managed to find ( in the github repo ) was a
>> JavaScript file which contained if I remember correctly, 2 definitions of
>> sorting algorithms.
>>
>> On Thu, 13 Sep 2018 at 16:23, @soylentgraham 
>> wrote:
>>
>>> You seem to be purposely ignoring the responses to your questions.
>>>
>>> If you still want help, build v8, build a program, breakpoint the
>>> function you want to see is called, debug it (this alone answers all your
>>> questions), then come back if you still have a VERY SPECIFIC question.
>>>
>>>
>>> On Thursday, 13 September 2018 15:15:03 UTC+1, dan Med wrote:

 No one is willingly to help me  ?

 On Wed, 12 Sep 2018 at 20:34, dan Med  wrote:

> Yeah i meant   ArrayBuffer*Builder*::Append my bad but when it is
> actually called in blink ?
> Cause by the name it has to do with Arraybuffers..
> Plus if i build v8 so i can examine the memory layout, where is the
> code on how v8 handeles arraybuffer ?
> Where is the doc or some source where there's explained how v8
> represents object in memory, how can i be sure that in memory i'm not
> starrying at a pointer instead of an object or something like that...
>
> Il giorno mer 12 set 2018 alle ore 19:40 Jakob Kummerow <
> jkum...@chromium.org> ha scritto:
>
>> On Wed, 12 Sep 2018 at 13:15, dan Med  wrote:
>>
>>> But can someone help me understand the arraybuffer part ? How to
>>> call arraybuffer::append and when I create an instance of a arraybuffer 
>>> it
>>> will create it with maximum size so 37... bytes and will only say that 
>>> the
>>> bytes used are the one which I’ve declared ?
>>>
>>
>> There is no ArrayBuffer::Append. Read closely: you've found
>> ArrayBuffer*Builder*::Append, which is some implementation detail in
>> Blink (not V8). I don't know when it's called, but I've pointed out 
>> before
>> how you can find out. When you use ArrayBuffer objects in JavaScript, 
>> then
>> that code is not executed at all.
>>
>> And when you create an ArrayBuffer(10) in JavaScript, it definitely
>> does not allocate 32KB of memory. It'll round up to the nearest multiple 
>> of
>> a pointer size.
>>
>> On Wed, Sep 12, 2018 at 10:09 AM dan Med  wrote:
>>
>>> Oh one more thing, so each tab in chrome is handeled as a single
>>> process, but Is the same process sandboxes with the Windows 10 kernel.
>>> Security or there’s another process which is sandboxes and then the main
>>> tab process the ( renderer ) is executed inside of it ?
>>>
>>
>> That's a completely unrelated question which has nothing to do with
>> V8 and does not belong in this thread. I suggest to look around on
>> http://dev.chromium.org/developers for a bunch of things that have
>> been explained before.
>>
>> On Wed, 12 Sep 2018 at 00:12, Peter Schow  wrote:

> On Tue, Sep 11, 2018 at 2:09 PM dan Med 
> wrote:
> >
> > Would you suggest to build v8 such that I can debug it as I want
> ?
>
> It's difficult to go wrong with this approach if you want to better
> understand V8 or any large, complex system.
>
> --
> --
> v8-users mailing list
> v8-u...@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 to v8-users+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> --
>>> v8-users mailing list
>>> v8-u...@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 to v8-users+u...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> --
>> v8-users mailing list
>> v8-u...@googlegroups.com
>> 

Re: [v8-users] Arraybuffer

2018-09-13 Thread dan Med
Still no one ?

On Thu, 13 Sep 2018 at 16:31, dan Med  wrote:

> Okay I will but, how could I be sure when blink on the renderer process
> executes arraybufferbuilder ??
> Or one more thing, can u redirect me to checkout how v8 represents data in
> memory, how would it handle arraybuffers?
> The only thing I’ve managed to find ( in the github repo ) was a
> JavaScript file which contained if I remember correctly, 2 definitions of
> sorting algorithms.
>
> On Thu, 13 Sep 2018 at 16:23, @soylentgraham 
> wrote:
>
>> You seem to be purposely ignoring the responses to your questions.
>>
>> If you still want help, build v8, build a program, breakpoint the
>> function you want to see is called, debug it (this alone answers all your
>> questions), then come back if you still have a VERY SPECIFIC question.
>>
>>
>> On Thursday, 13 September 2018 15:15:03 UTC+1, dan Med wrote:
>>>
>>> No one is willingly to help me  ?
>>>
>>> On Wed, 12 Sep 2018 at 20:34, dan Med  wrote:
>>>
 Yeah i meant   ArrayBuffer*Builder*::Append my bad but when it is
 actually called in blink ?
 Cause by the name it has to do with Arraybuffers..
 Plus if i build v8 so i can examine the memory layout, where is the
 code on how v8 handeles arraybuffer ?
 Where is the doc or some source where there's explained how v8
 represents object in memory, how can i be sure that in memory i'm not
 starrying at a pointer instead of an object or something like that...

 Il giorno mer 12 set 2018 alle ore 19:40 Jakob Kummerow <
 jkum...@chromium.org> ha scritto:

> On Wed, 12 Sep 2018 at 13:15, dan Med  wrote:
>
>> But can someone help me understand the arraybuffer part ? How to call
>> arraybuffer::append and when I create an instance of a arraybuffer it 
>> will
>> create it with maximum size so 37... bytes and will only say that the 
>> bytes
>> used are the one which I’ve declared ?
>>
>
> There is no ArrayBuffer::Append. Read closely: you've found ArrayBuffer
> *Builder*::Append, which is some implementation detail in Blink (not
> V8). I don't know when it's called, but I've pointed out before how you 
> can
> find out. When you use ArrayBuffer objects in JavaScript, then that code 
> is
> not executed at all.
>
> And when you create an ArrayBuffer(10) in JavaScript, it definitely
> does not allocate 32KB of memory. It'll round up to the nearest multiple 
> of
> a pointer size.
>
> On Wed, Sep 12, 2018 at 10:09 AM dan Med  wrote:
>
>> Oh one more thing, so each tab in chrome is handeled as a single
>> process, but Is the same process sandboxes with the Windows 10 kernel.
>> Security or there’s another process which is sandboxes and then the main
>> tab process the ( renderer ) is executed inside of it ?
>>
>
> That's a completely unrelated question which has nothing to do with V8
> and does not belong in this thread. I suggest to look around on
> http://dev.chromium.org/developers for a bunch of things that have
> been explained before.
>
> On Wed, 12 Sep 2018 at 00:12, Peter Schow  wrote:
>>>
 On Tue, Sep 11, 2018 at 2:09 PM dan Med 
 wrote:
 >
 > Would you suggest to build v8 such that I can debug it as I want ?

 It's difficult to go wrong with this approach if you want to better
 understand V8 or any large, complex system.

 --
 --
 v8-users mailing list
 v8-u...@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 to v8-users+u...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>> --
>> --
>> v8-users mailing list
>> v8-u...@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 to v8-users+u...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> --
> v8-users mailing list
> v8-u...@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 to v8-users+u...@googlegroups.com.


> For more options, visit https://groups.google.com/d/optout.
>
 --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> http://groups.google.com/group/v8-users
>> ---
>> 

[v8-users] Re: ChromeDevTools connected to Inspector, but error responses... missing native JS functions?

2018-09-13 Thread @soylentgraham
For any future readers;
I went back to trying to build a debug v8 set of libs (wouldnt compile 
before, added is_component_build=false which I think fixed that)
Built with latest master (4544e18b0c3845a9fca422cf0903df4803343cf1) 

Which forced me to correct a few uses of deprecated functions, including v8
::String::NewFromUtf8() with no isolate, so *possibly* that was the source 
of the crash re: scriptorigin. I now get an origin in CDT (kinda, it still 
breaks in a VMXX file)

Then asserts as before in "code that should never be reached" (see earlier 
in the thread)

[image: Screen Shot 2018-09-13 at 17.08.09.png]



On Wednesday, 12 September 2018 17:34:30 UTC+1, @soylentgraham wrote:
>
> With a lot of back & forth help from Ibon/hyperandroid, we've got a bit 
> further in working out which things are good, and which are bad. 
> Feels like we're close, but things are still unstable, and a bit 
> unresponsive.
>
> I can kinda break into the code (which only shows *this *in sources)
> Still get the assert above from trying to autocomplete too many times. 
> (albeit after a RunMessageLoop callback now)
> And if I add a script origin, I get a crash trying to stacktrace 
> (immediately when connecting, still trying to figure this out, as my 
> scriptorigin is okay)
>
> More stripped back version here (cutting more dependencies out, but all my 
> setup, inspector, frontend, messaging is in v8minimal.cpp)
> https://github.com/SoylentGraham/V8InspectorMinimal
>
> On Monday, 27 August 2018 13:49:37 UTC+1, @soylentgraham wrote:
>>
>> Through various sources (ie, googling & github) I've finally got a bit of 
>> a grasp of the flow for connecting chrome dev tools to my v8 app. (which is 
>> using a pretty recent HEAD build I've built myself with all default 
>> settings other than compiling as a static lib[s]. v8-version.h says 7.0.0.0)
>>
>> I connect via an explicit url (can't quite get json/list/ to show up in 
>> chrome yet)
>> *chrome-devtools://devtools/bundled/inspector.html?experiments=true=true=127.0.0.1:8008
>>  
>> *
>> (Not sure how relevant the v8only=true and experiments=true are, couldn't 
>> find any documentation on this)
>>
>> This connects to my websocket, and I pass all messages straight to 
>> *Session->dispatchProtocolMessage*
>>
>> My channel then gets *sendResponse's* in return, which I send back to 
>> chrome over my websocket.
>>
>> Chrome dev tools shows essentially an empty debugger, no sources, no 
>> console output, no errors...
>>
>> The responses my isolate/context sends back, suggest maybe I have some JS 
>> symbols/modules missing, which maybe I need to implement?
>> I'm kinda assuming this, as the debugger. methods succeed, but things 
>> like *Inspector.enable* (which I haven't found anyone implementing, but 
>> some people are implementing Inspector objects, just with different 
>> methods) fail
>>
>> *Chrome tools message: {"id":16,"method":"Inspector.enable"}*
>>
>> *Channel response: {"error":{"code":-32601,"message":"'Inspector.enable' 
>> wasn't found"},"id":16}*
>> Is this why chrome isn't proceeding with anything?
>> Am I supposed to implement these, or perhaps are they missing from my 
>> native blobs when I built my v8 libraries?
>>
>> My overloads of the inspector client functions like 
>> *runMessageLoopOnPause* aren't being called, but I assume that's just 
>> because I haven't gotten to any stage where commands are being evaluated?
>>
>> Below is what I get when I connect chrome, but then it just sits there :)
>>
>> Thanks for any pointers in the right direction!
>>
>> *Chrome tools message: 
>> {"id":1,"method":"Network.enable","params":{"maxPostDataSize":65536}}*
>>
>> *Channel response: {"error":{"code":-32601,"message":"'Network.enable' 
>> wasn't found"},"id":1}*
>>
>> *Chrome tools message: {"id":2,"method":"Page.enable"}*
>>
>> *Channel response: {"error":{"code":-32601,"message":"'Page.enable' 
>> wasn't found"},"id":2}*
>>
>> *Chrome tools message: {"id":3,"method":"Page.getResourceTree"}*
>>
>> *Chrome tools message: {"id":4,"method":"Profiler.enable"}*
>>
>> *Channel response: 
>> {"error":{"code":-32601,"message":"'Page.getResourceTree' wasn't 
>> found"},"id":3}*
>>
>> *Channel response: {"id":4,"result":{}}*
>>
>> *Chrome tools message: {"id":5,"method":"Runtime.enable"}*
>>
>> *Channel response: 
>> {"method":"Runtime.executionContextCreated","params":{"context":{"id":1,"origin":"","name":"PopEngineContextName"}}}*
>>
>> *Channel response: {"id":5,"result":{}}*
>>
>> *Chrome tools message: {"id":6,"method":"Debugger.enable"}*
>>
>> *Channel response: 
>> {"method":"Debugger.scriptParsed","params":{"scriptId":"9","url":"","startLine":0,"startColumn":0,"endLine":1,"endColumn":0,"executionContextId":1,"hash":"2a70962568dbbde00fb323decd63c2ca137b304c","isLiveEdit":false,"sourceMapURL":"","hasSourceURL":false,"isModule":false,"length":17}}*
>>
>> *Channel response: 
>> 

Re: [v8-users] Arraybuffer

2018-09-13 Thread dan Med
Okay I will but, how could I be sure when blink on the renderer process
executes arraybufferbuilder ??
Or one more thing, can u redirect me to checkout how v8 represents data in
memory, how would it handle arraybuffers?
The only thing I’ve managed to find ( in the github repo ) was a JavaScript
file which contained if I remember correctly, 2 definitions of sorting
algorithms.

On Thu, 13 Sep 2018 at 16:23, @soylentgraham 
wrote:

> You seem to be purposely ignoring the responses to your questions.
>
> If you still want help, build v8, build a program, breakpoint the function
> you want to see is called, debug it (this alone answers all your
> questions), then come back if you still have a VERY SPECIFIC question.
>
>
> On Thursday, 13 September 2018 15:15:03 UTC+1, dan Med wrote:
>>
>> No one is willingly to help me  ?
>>
>> On Wed, 12 Sep 2018 at 20:34, dan Med  wrote:
>>
>>> Yeah i meant   ArrayBuffer*Builder*::Append my bad but when it is
>>> actually called in blink ?
>>> Cause by the name it has to do with Arraybuffers..
>>> Plus if i build v8 so i can examine the memory layout, where is the code
>>> on how v8 handeles arraybuffer ?
>>> Where is the doc or some source where there's explained how v8
>>> represents object in memory, how can i be sure that in memory i'm not
>>> starrying at a pointer instead of an object or something like that...
>>>
>>> Il giorno mer 12 set 2018 alle ore 19:40 Jakob Kummerow <
>>> jkum...@chromium.org> ha scritto:
>>>
 On Wed, 12 Sep 2018 at 13:15, dan Med  wrote:

> But can someone help me understand the arraybuffer part ? How to call
> arraybuffer::append and when I create an instance of a arraybuffer it will
> create it with maximum size so 37... bytes and will only say that the 
> bytes
> used are the one which I’ve declared ?
>

 There is no ArrayBuffer::Append. Read closely: you've found ArrayBuffer
 *Builder*::Append, which is some implementation detail in Blink (not
 V8). I don't know when it's called, but I've pointed out before how you can
 find out. When you use ArrayBuffer objects in JavaScript, then that code is
 not executed at all.

 And when you create an ArrayBuffer(10) in JavaScript, it definitely
 does not allocate 32KB of memory. It'll round up to the nearest multiple of
 a pointer size.

 On Wed, Sep 12, 2018 at 10:09 AM dan Med  wrote:

> Oh one more thing, so each tab in chrome is handeled as a single
> process, but Is the same process sandboxes with the Windows 10 kernel.
> Security or there’s another process which is sandboxes and then the main
> tab process the ( renderer ) is executed inside of it ?
>

 That's a completely unrelated question which has nothing to do with V8
 and does not belong in this thread. I suggest to look around on
 http://dev.chromium.org/developers for a bunch of things that have
 been explained before.

 On Wed, 12 Sep 2018 at 00:12, Peter Schow  wrote:
>>
>>> On Tue, Sep 11, 2018 at 2:09 PM dan Med  wrote:
>>> >
>>> > Would you suggest to build v8 such that I can debug it as I want ?
>>>
>>> It's difficult to go wrong with this approach if you want to better
>>> understand V8 or any large, complex system.
>>>
>>> --
>>> --
>>> v8-users mailing list
>>> v8-u...@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 to v8-users+u...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> --
> v8-users mailing list
> v8-u...@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 to v8-users+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
 --
 --
 v8-users mailing list
 v8-u...@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 to v8-users+u...@googlegroups.com.
>>>
>>>
 For more options, visit https://groups.google.com/d/optout.

>>> --
> --
> 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 to v8-users+unsubscr...@googlegroups.com.
> For more 

Re: [v8-users] Arraybuffer

2018-09-13 Thread dan Med
No one is willingly to help me  ?

On Wed, 12 Sep 2018 at 20:34, dan Med  wrote:

> Yeah i meant   ArrayBuffer*Builder*::Append my bad but when it is
> actually called in blink ?
> Cause by the name it has to do with Arraybuffers..
> Plus if i build v8 so i can examine the memory layout, where is the code
> on how v8 handeles arraybuffer ?
> Where is the doc or some source where there's explained how v8 represents
> object in memory, how can i be sure that in memory i'm not starrying at a
> pointer instead of an object or something like that...
>
> Il giorno mer 12 set 2018 alle ore 19:40 Jakob Kummerow <
> jkumme...@chromium.org> ha scritto:
>
>> On Wed, 12 Sep 2018 at 13:15, dan Med  wrote:
>>
>>> But can someone help me understand the arraybuffer part ? How to call
>>> arraybuffer::append and when I create an instance of a arraybuffer it will
>>> create it with maximum size so 37... bytes and will only say that the bytes
>>> used are the one which I’ve declared ?
>>>
>>
>> There is no ArrayBuffer::Append. Read closely: you've found ArrayBuffer
>> *Builder*::Append, which is some implementation detail in Blink (not
>> V8). I don't know when it's called, but I've pointed out before how you can
>> find out. When you use ArrayBuffer objects in JavaScript, then that code is
>> not executed at all.
>>
>> And when you create an ArrayBuffer(10) in JavaScript, it definitely does
>> not allocate 32KB of memory. It'll round up to the nearest multiple of a
>> pointer size.
>>
>> On Wed, Sep 12, 2018 at 10:09 AM dan Med  wrote:
>>
>>> Oh one more thing, so each tab in chrome is handeled as a single
>>> process, but Is the same process sandboxes with the Windows 10 kernel.
>>> Security or there’s another process which is sandboxes and then the main
>>> tab process the ( renderer ) is executed inside of it ?
>>>
>>
>> That's a completely unrelated question which has nothing to do with V8
>> and does not belong in this thread. I suggest to look around on
>> http://dev.chromium.org/developers for a bunch of things that have been
>> explained before.
>>
>> On Wed, 12 Sep 2018 at 00:12, Peter Schow  wrote:

> On Tue, Sep 11, 2018 at 2:09 PM dan Med 
> wrote:
> >
> > Would you suggest to build v8 such that I can debug it as I want ?
>
> It's difficult to go wrong with this approach if you want to better
> understand V8 or any large, complex system.
>
> --
> --
> 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 to v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> --
>>> 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 to v8-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> --
>> 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 to v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.