Re: [v8-users] Debugger acting as a client connecting to the server

+yang who can say more about node. We (Ben, Yang & myself) recently discussed the possibility of adding coverage support to node itself. See here for a (very rough and early stage) doc with some

Re: [v8-users] OOM in Heap::ReserveSpace

Even without a repro, could you open a bug? It's easier to loop in people and discuss there. Thanks! On Sat, Jul 7, 2018 at 2:43 AM, Yvonne Chen wrote: > Actually, not mprotect. madvise, in ReclaimInaccessibleMemory, with both > MADV_FREE and MADV_DONTNEED calls failing, both with error code

Re: [v8-users] Building in linux, either v8_libplatform and v8_libbase are all I get, or they're the only things that are missing!

Did you see https://github.com/v8/v8/wiki/Building-from-Source? To build all targets, just use: $ ninja -C out.gn/golib/ On Fri, Apr 20, 2018 at 7:25 AM, Andrew Walker wrote: > I am attempting to build v8 in a wheezy VM for a binding that links > against > >- libv8 >

Re: [v8-users] What is the memory layout of a code object in V8?

Have a look at [0], which describes the memory layout of code objects. The RelocInfo is currently a separate object and Code objects store a pointer to it. [0] https://cs.chromium.org/chromium/src/v8/src/objects/code.h?l=369=ff6b34b468c1eae8589b278923f87e2f573bc248 On Thu, Apr 19, 2018 at 11:57

Re: [v8-users] mksnapshot and warm_up

AFAIK that's correct. The polluted warmup context is thrown out, and a second clean context (with the now-compiled code) is serialized into the warmed up snapshot. On Thu, Mar 1, 2018 at 5:31 PM, Johannes Rieken wrote: > Great! Thanks for the speedy reply. Looking at

Re: [v8-users] mksnapshot and warm_up

On Thu, Mar 1, 2018 at 4:43 PM, Johannes Rieken wrote: > > Hey, > > Can someone help me understand what the difference between a warm and cold > snapshot is? I stumbled over `WarmUpSnapshotDataBlob` but I am not > entirely sure how to make use of them via the

Re: [v8-users] Lazy deserialization

On Fri, Feb 16, 2018 at 5:09 PM, Chris Dumoulin wrote: > Thanks for the reply Jakob. I'll give your code changes a try. > I'm currently trying this on Mac OS X x64. > > I'm pretty sure I'm using a snapshot build. Is there an easy way to tell > for sure? > Snapshot builds are

Re: [v8-users] Lazy deserialization

On Thu, Feb 15, 2018 at 9:28 PM, Chris Dumoulin wrote: > I'm interested in minimizing v8 memory usage, and I recently saw this blog > post on Lazy Deserialization: https://v8project.blogspot.ca/2018/02/ > lazy-deserialization.html > > I've built and run samples/hello-world.cc

Re: [v8-users] Advice for submitting a PR to fix Debug::ArchiveDebug and Debug::RestoreDebug?

On Mon, Dec 18, 2017 at 9:39 PM, Ben Noordhuis wrote: > On Mon, Dec 18, 2017 at 9:06 PM, Ben Newman wrote: > > Hi folks! This is my first time posting here, so please let me know if I > > should ask this question somewhere else instead. I'm asking here

Re: [v8-users] Query regarding file size of snaphot_blob.bin

On Tue, Dec 19, 2017 at 7:25 AM, wrote: > Hi Jakob, > > We were comparing v8/src/builtins.h file of Chromium M47 and Chromium M56 > and found that there many new (>100) builtin functions added in Chromium 56. > > Do you think this could be one of the major reasons for

Re: [v8-users] Query regarding file size of snaphot_blob.bin

On Mon, Dec 18, 2017 at 6:20 AM, wrote: > >* new functionality (both internal and new language additions); > > Is it possible to find out what new functionality has been added?( If > yes please can you let me know where to check for new features added ?) > For new

Re: [v8-users] Query regarding file size of snaphot_blob.bin

On Thu, Dec 14, 2017 at 10:39 AM, wrote: > On Thursday, December 14, 2017 at 2:44:15 PM UTC+5:30, Ben Noordhuis wrote: >> >> On Thu, Dec 14, 2017 at 7:22 AM, wrote: >> > 1) How is snapshot_blob.bin generated at compile time ? (If possible >>

Re: [v8-users] Query regarding file size of snaphot_blob.bin

We've actually been working on reducing memory overhead around the snapshot, see the lazy builtins design doc at http://goo.gl/dxkYDZ. Note though that this is intended to reduce runtime memory use, not the size of the snapshot blob itself. I'd expect the snapshot blob to grow further in the

Re: [v8-users] How to compile V8 for X86_64 platform?

Hi Sameer, the V8 build process is documented at https://github.com/v8/v8/wiki/Building-with-GN. Cheers, Jakob On Wed, Jul 5, 2017 at 7:20 AM, Sameer wrote: > Hi, > > I am new to V8 world. > Could you please help how do I compile V8 for X86_64 platforms? > I am

Re: [v8-users] Re: Significant JSON::Stringify, Uint8Array, or ArrayBuffer changes between v5.4 to v6.0.186

Interesting. It'd be very helpful if you could open a bug at crbug.com/v8/new with a full code example (including build instructions if it includes C++) and instructions to reproduce the issue. Feel free to assign it to me (jgru...@chromium.org) and I'll have a look. On Mon, Jun 26, 2017 at 6:44