Re: [v8-users] Memory leak on script crash

2017-05-01 Thread Brendan Bates
, 2017 at 5:20 PM, Brendan Bates > wrote: > > I have a question in response to this then. How would you handle a > dynamic > > multi-indexed field mapped to a C++ object? Currently we have a root > > ObjectTemplate with an > > indexed property handler that kn

Re: [v8-users] Memory leak on script crash

2017-05-01 Thread Brendan Bates
at assumption, but I assumed most things stored in a Local were memory leak safe. On Monday, May 1, 2017 at 11:41:46 AM UTC-4, Ben Noordhuis wrote: > > On Mon, May 1, 2017 at 5:20 PM, Brendan Bates > wrote: > > I have a question in response to this then. How would you handle a &g

Re: [v8-users] Memory leak on script crash

2017-05-01 Thread Brendan Bates
Also @Gautham B A we have not figured out a good solution yet - still reviewing the best way to actually get around this. On Monday, May 1, 2017 at 11:20:55 AM UTC-4, Brendan Bates wrote: > > Seems relevant enough to me if you like efficient programs >> > > Oh I definitely ag

Re: [v8-users] Memory leak on script crash

2017-05-01 Thread Brendan Bates
#x27;t run some stress tests on our system. I wrote a test that generates tens of MB per second (even when calling LowMemoryNotification) from using this behavior. On Monday, May 1, 2017 at 11:08:01 AM UTC-4, Ben Noordhuis wrote: > > On Mon, May 1, 2017 at 4:25 PM, Brendan Bates > wr

Re: [v8-users] Memory leak on script crash

2017-05-01 Thread Brendan Bates
Hey Gautham B A, I am currently experiencing a similar issue. I have found that using NewInstance() causes a slow memory growth/leak in our application. We aggressively call LowMemoryNotification() on our scripts, as they are meant to run for a very long time and accept the performance trade

Re: [v8-users] Re: Isolate Creation Times

2017-02-24 Thread Brendan Bates
provide the > gn args you used for building? > > Thanks > Jochen > > Brendan Bates > schrieb am Do., 23. > Feb. 2017, 18:07: > >> I should also note that I can replicate this by simply running the d8 >> executable, which seems to take about 5 seconds to bo

[v8-users] Re: Isolate Creation Times

2017-02-23 Thread Brendan Bates
I should also note that I can replicate this by simply running the d8 executable, which seems to take about 5 seconds to bootstrap. On Thursday, February 23, 2017 at 10:59:47 AM UTC-5, Brendan Bates wrote: > > I'm posting here to see if anyone has experienced this recently. > >

[v8-users] Isolate Creation Times

2017-02-23 Thread Brendan Bates
I'm posting here to see if anyone has experienced this recently. We upgraded our scripting environment from *5.1.281.65 *to *5.7.492.44*. Everything as far as building with GN has gone smoothly, however one odd issue is with the timing of the isolate creation: _isolate = Isolate::New(createPa

Re: [v8-users] Re: Building with MSVC & GN - Where do the static files go?

2017-02-20 Thread Brendan Bates
libs from the >>> obj-files using the MSVC lib tool manually. >>> >>> Unsatisfactory, but it was working for me. >>> >>> Am Montag, 9. Januar 2017 15:55:40 UTC+1 schrieb Brendan Bates: >>>> >>>> Hello, >>>> >>>

[v8-users] Building with MSVC & GN - Where do the static files go?

2017-01-09 Thread Brendan Bates
Hello, I have seen this issue pop up a couple times on here and wondering what the current status is. I was spending the morning trying to get ahead of the game and switch from a Gyp build to a GN build. We are using MSVC 2015 to perform the build. I am successfully configuring and building

[v8-users] Re: Building with MSVC & GN - Where do the static files go?

2017-01-09 Thread Brendan Bates
I should also specify, this specific build is using the current Win32 stable version 5.5.372.32. -- -- 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 uns

Re: [v8-users] Re: Library size when built with mingw

2016-05-12 Thread Brendan Bates
Update - Holy Guacamole, I've gotten v8 to build with MinGW! Never thought I'd see this day come again. I actually went a slightly different route with it - here are the things I changed: 1. Apply the forking.py fix to depot_tools instead of v8. 2. REMOVE lines 73 and 78 in the mingw-gene

Re: [v8-users] Re: Library size when built with mingw

2016-05-12 Thread Brendan Bates
t; you want to test it and let me know that would be great. If everything > seems functional with the code changes I'll work on clean up and getting > them pushed upstream. > > Thanks > > On Wednesday, May 11, 2016 at 11:50:30 AM UTC-6, Brendan Bates wrote: >> >>

Re: [v8-users] Re: Library size when built with mingw

2016-05-11 Thread Brendan Bates
13 toolchain. > > On Wednesday, May 11, 2016, Brendan Bates > wrote: > >> Hey Zac, >> >> I'm also trying to build on MinGW right now. I have successfully built >> on MSVC2015 but would much prefer MinGW (as all of our other products run >> under

[v8-users] Re: Library size when built with mingw

2016-05-11 Thread Brendan Bates
Hey Zac, I'm also trying to build on MinGW right now. I have successfully built on MSVC2015 but would much prefer MinGW (as all of our other products run under MinGW in Windows). I have had no luck thus far, have you been able to successfully build yet? I personally haven't got very far...