Re: [v8-users] CpuProfile ->.cpuprofile.

Now located here: https://chromium.googlesource.com/chromium/src.git/+/master/third_party/WebKit/Source/platform/v8_inspector/V8HeapProfilerAgentImpl.cpp On Thursday, December 10, 2015 at 10:12:44 AM UTC-8, Jim Acquavella wrote: > > I believe your goal is to write a version of the cpup

[v8-users] Profiling Data contains no line ticks (line and timing information)

Every single CpuProfileNode returns a zero when I call GetHitLineCount(). I was able to look at the Chromium source code and figure out how to turn the binary data to a .cpuprofile file I can load and visualize in Chrome. I've attached an example, but as you can see, there's no timing or hit

Re: [v8-users] Profiling Data contains no line ticks (line and timing information)

gt; running into. One thing I could imagine is that you didn't have the > profiler engaged while the code was compiled. In this case, you won't get > per line hit counts. > > On Tue, Mar 29, 2016 at 8:39 PM Jim Acquavella > wrote: > >> Every single CpuProfileNode retur

[v8-users] Re: error while building v8 in visual studio express 2013

I'm also seeing the error above, but only intermittently. If I build from the command line, I will often see the problem, but if I open the IDE and build, no errors. Seems like a race condition, because subsequent builds do succeed. I've attached the script I'm using to acquire v8 and tools o

[v8-users] Compiling with libc++

I'm trying to compile my app with libc++ and am linking with the v8 static libraries on the mac. libstdc++ compiles and links without a problem. libc++ generates the following errors. Any advice? (null): "std::string::end() const", referenced from: (null): V8::internal::compiler::operator<<

[v8-users] Re: Compiling with libc++

I was able to sole this using : python build/gyp_v8 -Dtarget_arch=x64 -Dsnapshot=off -Dv8_use_external_startup_data=0 -Dclang=1 -Dhost_clang=1 -Duse_custom_libcxx=1 -Dmac_deployment_target=10.10 On Sunday, August 7, 2016 at 8:44:23 PM UTC-7, Jim Acquavella wrote: > > I'm trying to

[v8-users] Re: Compiling with libc++

I was able to solve this with the following gyp args: python build/gyp_v8 -Dtarget_arch=x64 -Dsnapshot=off -Dv8_use_external_startup_data=0 -Dclang=1 -Dhost_clang=1 -Duse_custom_libcxx=1 -Dmac_deployment_target=10.10 -- -- v8-users mailing list v8-users@googlegroups.com http://groups.goog

[v8-users] InitializeICUDefaultLocation path string representation.

Is this api expecting a utf8 string or ansi? bool v8::V8::InitializeICUDefaultLocation ( const char * exec_path, const char * icu_data_file = nullptr ) It would be sort of ironic if the exec p

Re: [v8-users] InitializeICUDefaultLocation path string representation.

, Sep 6, 2018 at 4:41 PM Jim Acquavella wrote: > Is this api expecting a utf8 string or ansi? > > > bool v8::V8::InitializeICUDefaultLocation ( const char * exec_path, > const char * icu_data_file = nullptr > <https://v8.paulfryzel.com/docs/master/fla

Re: [v8-users] InitializeICUDefaultLocation path string representation.

Yeah, I can avoid this by placing the icu file next to my executable. In the future, this should definitely use LoadLibraryW. Thanks. On Tue, Oct 2, 2018 at 4:11 AM Ben Noordhuis wrote: > On Fri, Sep 7, 2018 at 1:41 AM Jim Acquavella > wrote: > > Is this api expecting a utf8 st

Re: [v8-users] C++ lifetime management via shared_ptr and

Thanks Stephan! I'm surprised and disappointed I can't guarentee my C++ objects will be destroyed. Can anyone from Google comment on this? There must be a way to force everything allocated to be released at shutdown, no?! On Fri, May 24, 2013 at 8:35 AM, Stephan Beal wrote: > On Fri, May 24,

Re: [v8-users] C++ lifetime management via shared_ptr and

C++ b.exe!v8::V8::LowMemoryNotification() Line 4968 C++ On Sun, May 26, 2013 at 11:38 PM, Sven Panne wrote: > On Sat, May 25, 2013 at 4:36 AM, Stephan Beal wrote: > >> >> On Fri, May 24, 2013 at 9:58 PM, Jim Acquavella wrote: >> >>> Thanks Stephan! I'm surprised and d

Re: [v8-users] C++ lifetime management via shared_ptr and

Thanks Mike M! My solution above does seem to currently work, but the fact that Sven states this won't be guaranteed to work in the future is disappointing. I expect the javascript objects in the heap that reference my C++ objects to be cleaned up when I quit my application. In doing so, I want

Re: [v8-users] C++ lifetime management via shared_ptr and

As it stands now in my test code, it is optional because I'm calling v8::V8::LowMemoryNotification(); before v8::V8::Dispose(); If you want fast shutdown, don't call either! Win, Win! On Wed, Jun 12, 2013 at 3:35 PM, Mike Moening wrote: > > > "But it's not going to be at the v8 level." A few y

Re: [v8-users] C++ lifetime management via shared_ptr and

So, myth #5 in the slides seems like the thing that would most likely cause v8 to not know whether objects are marked as unreachable. If I have a context, and a handle scope, that contains objects that reference each other, can't you determine the objects are unreachable if their parent context an

[v8-users] Mac Debugging -> Failed to connect to Standalone V8 VM Connection refused

I've seen others post this problem, but I don't see a solution that is helping me. I'm working on a cross platform application and was able to get debugging via Eclipse working on windows. On the mac, when I try and connect, Eclipse will report: Failed to connect to Standalone V8 VM Connection

[v8-users] XCode 4.6.3 compile problem (no assembler installed) - Help!

I've tried this on 2 macs running XCode 4.6.3 and both have the same errors. Following V8 build instructions at a command prompt: svn checkout http://v8.googlecode.com/svn/trunk/ v8 cd v8 make dependencies build/gyp_v8 -Dtarget_arch=x64 xcodebuild -project build/all.xcodeproj Here are the resul

Re: [v8-users] XCode 4.6.3 compile problem (no assembler installed) - Help!

my iPhone On Aug 9, 2013, at 1:06 AM, Jakob Kummerow wrote: > Sounds like an issue with you Xcode installation(s), specifically that it > can't produce x64 binaries. I don't think there's anything V8 can do about > this. > > > On Thu, Aug 8, 2013 at 10:34 PM

Re: [v8-users] XCode 4.6.3 compile problem (no assembler installed) - Help!

Still waiting for someone to try this and confirm the issue. Anyone using XCode 4.6.3? What versions of XCode are folks using? Thanks. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to th

Re: [v8-users] XCode 4.6.3 compile problem (no assembler installed) - Help!

; > mschwartz@dionysus:~$ ls -l > /Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/as > lrwxr-xr-x 1 root wheel 21 Jul 25 2012 > /Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/as > -

Re: [v8-users] XCode 4.6.3 compile problem (no assembler installed) - Help!

; /Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/as >> -> ../../../../../bin/as >> >> >> On Aug 8, 2013, at 1:34 PM, Jim Acquavella wrote: >> >>> /Applications/Xcode.app/Contents/Developer/usr/llvm

Re: [v8-users] XCode 4.6.3 compile problem (no assembler installed) - Help!

Still not working. Here's my build script.. svn checkout --force http://v8.googlecode.com/svn/trunk/ v8 cd v8 make dependencies build/gyp_v8 -Dtarget_arch=x64 xcodebuild -project build/all.xcodeproj On Tue, Aug 13, 2013 at 7:09 PM, Jim Acquavella wrote: > Definitely did that! A

Re: [v8-users] XCode 4.6.3 compile problem (no assembler installed) - Help!

I created a VM with a clean installation of OSX 10.8 and v8 built without errors. I then installed some of the other software I use (like the Intel Compiler) and it was also fine. I then compared the installation of the machine that was and wasn't compiling and found that the /Applications/

Re: [v8-users] Re: Making v8::Persistent safe to use

Why can't the Persistent use a RIAA pattern that's reference counted? Ideally, I'd like to create a persistent, copy it to another persistent (which would increment the reference), then the last one to go out of scope should be disposed automatically in the destructor. In other words, I'd li

Re: [v8-users] Re: Making v8::Persistent safe to use

:operator=(other); > } > protected: > void CheckDispose() > { > if (!v8::Persistent::IsEmpty()) > { > v8::Persistent::Dispose(); > v8::Persistent::Clear(); > }

Re: [v8-users] Re: Making v8::Persistent safe to use

e disposed. Make sense? On Thu, Aug 22, 2013 at 11:37 PM, Dan Carney wrote: > On Friday, August 23, 2013 12:12:31 AM UTC+2, Jim Acquavella wrote: > >> Why can't the Persistent use a RIAA pattern that's reference counted? >> Ideally, I'd like to create a persiste

Re: [v8-users] Re: Making v8::Persistent safe to use

Is calling MakeWeak on an already weak handle something that needs to be supported? I'd say you add a clone method and have the items that force storage cell duplication return an error. Supporting common use case that makes these easy to use should be the goal. On Tue, Aug 27, 2013 at 9:34 AM,

[v8-users] python build/gyp_v8 -Dtarget_arch=x64 -Dcomponent=shared_library

This doesn't build on Windows. Anyone else seeing this? I'm getting lots of errors related to inconsistent dll linkage and when building all the v8 stuff, not my stuff. With a few modifications to v8 source, it now works. But, I don't think you'll want my changes! -J -- -- v8-users mailing

[v8-users] Re: python build/gyp_v8 -Dtarget_arch=x64 -Dcomponent=shared_library

> > Doesn't build on mac either... Ld ../xcodebuild/Debug/lineprocessor normal x86_64 cd /Users/jacquave/dev/animal/sandboxes/jacquave/v1/shared/third_party/v8/samples setenv MACOSX_DEPLOYMENT_TARGET 10.5 /Applications/Xcode.app/Contents/Developer/usr/bin/llvm-g++-4.2 -arch x86_

Re: [v8-users] Re: Making v8::Persistent safe to use

I started using this: template struct PersistentP : public boost::shared_ptr > { typedef boost::shared_ptr > _inherited; PersistentP(v8::Persistent *inPersistentP0 = NULL) { _inherited::reset(inPersistentP0); } v8::Local GetLocal() const { return v8::Local::New(v8::Isolate::GetCurrent(), *_inheri

Re: [v8-users] Re: python build/gyp_v8 -Dtarget_arch=x64 -Dcomponent=shared_library

Getting closer. Here are my windows errors: d:\dev\animal\sandboxes\jacquave\v1\shared\third_party\projects\v8\v8>"c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.com" /build Debug build\All.sln Microsoft (R) Visual Studio Version 10.0.40219.1. Copyright (C) Microsoft

[v8-users] msvcprtd.lib(MSVCP100D.dll) : error LNK2005: "public: static __int64 __cdecl std::numeric_limits<__int64>::max(void)" (?max@?$numeric_limits@_J@std@@SA_JXZ) already defined in v8_base.x64.l

I'm no longer able to link with the static libraries on windows. Anyone else running into this? It worked last time I updated about a month ago... 1>msvcprtd.lib(MSVCP100D.dll) : error LNK2005: "public: static __int64 __cdecl std::numeric_limits<__int64>::max(void)" (?max@?$numeric_limits@_J

[v8-users] Re: msvcprtd.lib(MSVCP100D.dll) : error LNK2005: "public: static __int64 __cdecl std::numeric_limits<__int64>::max(void)" (?max@?$numeric_limits@_J@std@@SA_JXZ) already defined in v8_base.x

Seems related to icu? https://bugzilla.mozilla.org/show_bug.cgi?id=899948 I'm not sure how this workaround applies to v8. Any help would be great since I can't workaround this issue using DLLs since they don't build at the moment. -- -- v8-users mailing list v8-users@googlegroups.com http:/

Re: [v8-users] Re: python build/gyp_v8 -Dtarget_arch=x64 -Dcomponent=shared_library

Tried adding the export line, but still have errors: === BUILD AGGREGATE TARGET v8_snapshot Support OF PROJECT v8 WITH THE DEFAULT CONFIGURATION (Debug) === Check dependencies PhaseScriptExecution "Action \"run_mksnapshot\"" "../../xcodebuild/v8.build/Debug/v8_snapshot Support.build/Script-969

Re: [v8-users] Re: python build/gyp_v8 -Dtarget_arch=x64 -Dcomponent=shared_library

Actually, that appears to work. But shell, process, lineprocessor and d8 don't link as stated. I'll try and get my app linking with the dylibs. Thanks. On Mon, Oct 14, 2013 at 10:53 AM, Jim Acquavella wrote: > Tried adding the export line, but still have errors: > > &g

[v8-users] has_pending_message_ causing V8_Fatal

Upon launching my app, if the script has an error, my application will fail with the stack crawl below. Within freeing the ThreadLocalTop, the ASSERT for !has_pending_message_ fails. Why is that? In my code that compiles and executes the script, it uses a TryCatch and asks whether is "HasCa

Re: [v8-users] has_pending_message_ causing V8_Fatal

Anyone? On Thu, May 29, 2014 at 2:37 PM, Jim Acquavella wrote: > Upon launching my app, if the script has an error, my application will > fail with the stack crawl below. Within freeing the ThreadLocalTop, the > ASSERT for !has_pending_message_ fails. Why is that? In my code that &

Re: [v8-users] has_pending_message_ causing V8_Fatal

CanContinue returns true. HasTerminated returns false. Seems normal... On Thu, Jun 5, 2014 at 2:42 AM, Ben Noordhuis wrote: > On Thu, May 29, 2014 at 11:37 PM, Jim Acquavella > wrote: > > Upon launching my app, if the script has an error, my application will > fail >

[v8-users] Re: Profiler crash

Were you able to solve this? I'm seeing the same. On Thursday, March 7, 2013 at 5:39:15 AM UTC-8, Damien Gleizes wrote: > > Hi all, > > I am trying to work with the profiler API but I get an unexpected crash: I > am probably doing something wrong but I can't figure what.. any help or > hints wo

Re: [v8-users] Profiler: Application crash in HandleProfilerSignal

I'm seeing this same problem when I start cpu profiling. In my case, StackFrameIteratorBase::SingletonFor is calling executing this line with a type of 0x2100. StackFrame* result = SingletonFor(type); SingletonFor returns NULL and DCHECK fails. On Tuesday, December 1, 2015 at 8:30:01 AM

Re: [v8-users] Profiler: Application crash in HandleProfilerSignal

Also, I can provide a binary with instructions on how to reproduce the problem. I'm using v8 version 4.5.35. On Wednesday, December 9, 2015 at 4:12:08 PM UTC-8, Jim Acquavella wrote: > > I'm seeing this same problem when I start cpu profiling. In my > case, Sta

Re: [v8-users] CpuProfile ->.cpuprofile.

I wish V8 would do this for us. I'm about to implement this as well, though v8 is crashing soon after I start profiling (addressed in another thread). I would recommend you download the Chromium source and look at how it converts from V8's cpu profile data into the file. See chromium\src\t

Re: [v8-users] CpuProfile ->.cpuprofile.

I believe your goal is to write a version of the cpuprofile file that is compatible with the latest Chrome. In that case, you should just match the current Chromium implementation: https://chromium.googlesource.com/chromium/src.git/+/master/third_party/WebKit/Source/core/inspector/v8/V8ProfilerAg

Re: [v8-users] Profiler: Application crash in HandleProfilerSignal

>>> 20 0x705fed58 >>> 19 0x380e93a33ca4 >>> 18 0x2c9f540abaf1 >>> 17 0x133cbc037991 >>> 16 0x133cbc0379b9 >>> 15 0x133cbc0379b9 >>> 14 0x2c9f540abaf1 >>> 13 0x00

Re: [v8-users] Profiler: Application crash in HandleProfilerSignal

Any help would be greatly appreciated. Has anyone from google been able to confirm the problem? Is it working for others? On Mon, Dec 14, 2015 at 8:21 AM, Jim Acquavella wrote: > Both my debug and optimized builds are crashing while advancing the > SafeStackFrameIterator

Re: [v8-users] Profiler: Application crash in HandleProfilerSignal

Run() Line 154 C++ v8.dll!v8::base::Thread::NotifyStartedAndRun() Line 468 C++ v8.dll!v8::base::ThreadEntry(void * arg) Line 1304 C++ [External Code] On Mon, Jan 11, 2016 at 10:01 AM, Jim Acquavella wrote: > Any help would be greatly appreciated. Has anyone from google been able >

Re: [v8-users] Profiler: Application crash in HandleProfilerSignal

I've filed this as a bug: https://bugs.chromium.org/p/v8/issues/detail?id=4705&can=2&q=4705&colspec=ID%20Type%20Status%20Priority%20Owner%20Summary%20HW%20OS%20Component%20Stars -Jim -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You r

Re: [v8-users] Profiler: Application crash in HandleProfilerSignal

rg) Line 1304 C++ [External Code] On Wed, Jan 27, 2016 at 9:42 AM, Jochen Eisinger wrote: > A fix was landed here: > https://chromium.googlesource.com/v8/v8.git/+/d11b44ec69c718a9b3b11872e7638c5675abd02c > does > that resolve your issue? > > On Mon, Jan 25, 2016 at 10:47 PM Jim Acquavell

Re: [v8-users] Re: Intermittent crashing creating a Persistent object.

Oh, single-threaded. I would have expected v8 to use a mutex around their persistent (global handle) management. I'll try a mutex on my side and see if that resolves the issue. Thanks for your help. 🤞 On Fri, Aug 26, 2022 at 12:52 AM dinf...@chromium.org wrote: > Hi, > > Those persistent/glo