Hi there,
I am upgrading my projects to v8 10.x, and found that
VisitHandlesWithClassIds has been deprecated, e.g. I can't call it anymore.
What is the current approach to clean up Persistent (weak or not) with
class id handles ?
Thanks.
--
--
v8-users mailing list
v8-users@googlegroups.com
I recently had a problem where a Persistent was being initialised in one
Isolate which was then disposed. I accidentally kept an initialised
Persistent around and got an immediate crash when calling Persistent Reset
after creating a 2nd Isolate.
In my case I was neglecting to Reset properly one
try searching for -DV8_COMPRESS_POINTERS in the archives of
> this list.
>
>
> On Sat, Dec 12, 2020 at 9:10 PM ibon wrote:
>
>> Hi folks.
>>
>> I have been trying to upgrade my app from v8 7.3 to 8.x.
>> The app is an android app, where an embedded v8 runs several
Hi folks.
I have been trying to upgrade my app from v8 7.3 to 8.x.
The app is an android app, where an embedded v8 runs several different
games.
Compilation of the libraries is successful. While armeabi-v7a and x86 libs
work seamlessly, the arm64-v8a library consistently crashes. Tried this as
Update:
I have tried compiling again the same exact version That did work before
(8.0.426.9) and I get the same error.
I run `gclient sync` before compiling the new version. Might this be the
culprit ?
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-user
Hi folks,
I have compiled 8.4-lkgr v8 (8.4.371.7) for Android, and I am getting the
following crash at runtime.
I could supply the full stacktrace, but it is already clear this happens at
Isolate initialization time.
Last time I compiled v8, was 8.0-lkgr arm7/arm64 and it turned out just
fine.
I definitely can start a debug session at any given time.
Simple question is whether you have set a valid ScriptOrigin when compiling
the string. I remember having trouble by not setting properly a valid
protocol name for the parsed script.
El martes, 5 de mayo de 2020, 11:29:09 (UTC+2), toto tt
Hi Darin,
I do embed v8 on android on a regular basis.
Unlike you, I run v8 bound to gl thread, and as a rule of thumb for
performance reasons always on a different than the main thread.
I need to, at least, run `v8::platform::PumpMessageLoop(&platform,
isolate_);` to have promises executed.
I
Hi there,
I recently upgraded my Android embedded v8 from 6.3 to 7.2.
I found that live editing code in Chrome Dev Tools crashes my app. All
other debugging related stuff works great, but this specific use case ends
up in an UNIMPLEMENTED code path inside
DefaultWorkerThreadsTaskRunner::PostDel
I get the same sequence of messages, and I don't need to implement anything
about them to have a fully functional debugging session between embedded v8
(android) and chrome dev tools.
El lunes, 27 de agosto de 2018, 14:49:37 (UTC+2), Graham Reeves escribió:
>
> Through various sources (ie, googl
I avoid linker problems by properly sorting the libraries.
The linker is sequential, and will fail if a given symbol is not present by
the time it is referenced, regardless it is in another to link lib.
This is a sort order that worked for me.
v8_base v8_libplatform v8_libbase v8_libsampler v8_s
Hi there,
while embedding v8, I have two modes of loading code.
One is using a remote web server to serve the requests.
Setting ScriptOrigin, makes on-demand map files loading to happen from the
same script origin, and hence I get a nice debugging session.
The problem comes from the second wo
> *SetCallAsFunctionHandler()* on the *ObjectTemplate*, it stops working
> and starts showing up as *f anonymous()*. I need this because I want to
> further call the object as a function.
> ibon, can you please check if *SetCallAsFunctionHandler()* is set for
> your *ObjectTemplate*?
&g
Have you tried setting the class name in the FunctionTemplate ?
interface_template->SetClassName( v8::String )
This names my objects as expected. I also get [object MyObject] instead of
[object Object] when calling Object's prototype toString.
You also might want to name the prototype by setting
Hey, I do this all the time with android studio.
I have an android app with embedded v8, and debug both native c++ and
javascript seamlessly.
El martes, 8 de mayo de 2018, 6:35:12 (UTC+2), Anoop R. S. escribió:
>
> Hi All,
> I am trying out a debugger prototype using the remote debugger protocol.
May 8, 2018 at 1:19 AM, ibon >
> wrote:
> > For my embedding needs, sometimes i need to keep a native wrapped object
> > alive.
> > Normally, I set a Persistent ref where i install a finalisation callback
> > with custom wrapper class is. This gives me fine control o
or keeping objects alive ?
Thanks.
- ibon
--
--
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 ema
I have an android app with v8 arm7 embedded. It runs on android 7.0, with
v8 6.3.292
I use chrome for remote dev tools debugging.
With current Chrome 66 on OSX 10.13.3, the new dev tools Performance tab
gets stuck 'Loading profile' after any profiling session.
The Previous Javascript Profiler (
you might want to try building your objects not from the InstanceTemplate,
but from the Interface template itself in Wrap as:
functionTemplate->GetFunction()->NewInstance()
El viernes, 2 de febrero de 2018, 12:32:21 (UTC+1), Cvetan Stefanovski
escribió:
>
> Hello,
>
> I am using V8 to expose
On Ubuntu 16 (virtualbox vm)
$ uname -a
Linux ibon-vb 4.10.0-28-generic #32~16.04.2-Ubuntu SMP Thu Jul 20 10:19:48
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
I am having some trouble compiling v8 lkgr branch with the following error:
ninja -C out.gn/android_arm.release -j 4
ninja: Entering
There's no problem in creating as much Context objects as needed per
Isolate.
When trying to detach an object from a context to reference it from another
one, make sure both context objects share the same security token
(SetSecurityToken) otherwise the operation will fail.
I don't really see wh
Hey Harsha,
you might want to have a look at chromium inspector test
here: https://cs.chromium.org/chromium/src/v8/test/inspector/
I have done integration of v8 embedded in android following that process
flawlessly.
Whenever you read front-end, translate to chrome dev tools (front-end). I
did
after compilation, you only get two thin libraries. You must create fat
libraries from compiled sources. This is what i do:
cd out.gn/myandroid/obj // or where you compiled v8 as a result of the ninja
call.
mkdir libs
cd libs
ar -rcsD libv8_base.a ../v8_base/*.o
ar -rcsD libv8_libbase.a ../v8_l
), Dzung Tran escribió:
>
> Can you tell me where can I find this LOCAL_STATIC_LIBRARIES in v8
> directory to modify?
> I am getting the same error. I am surprise this is not fix in the v8 repo.
>
> On Tuesday, November 1, 2016 at 1:06:37 PM UTC-7, ibon tolosana wrote:
>>
>>
v8-debugger.cc?rcl=1482193199&l=485
> [3]
> https://cs.chromium.org/chromium/src/v8/src/inspector/v8-debugger.cc?rcl=1482193199&l=491
> [4]
> https://cs.chromium.org/chromium/src/v8/src/inspector/v8-debugger.cc?rcl=1482193199&l=493
>
> Thanks,
> Aleksey.
>
> O
Hi,
i have successfully integrated remote debugging through chrome dev tools to
an embedded v8 in an android app.
I can see v8's loaded source code, do profiling, memory dumps, etc., but JS
debugging is not working as expected.
Whenever the debugger hits a breakpoint, the session channel sends
needs
2. libplatform
3. libbase
4. libsampler
With this, all linker symbols are found correctly:
LOCAL_STATIC_LIBRARIES := v8_base v8_nosnapshot v8_libplatform v8_libbase
v8_libsampler
Thanks.
El martes, 1 de noviembre de 2016, 21:06:37 (UTC+1), ibon tolosana escribió:
>
&
Hi Rodolph,
yes, I did follow that instructions.
What surprises me most is that v8::base::SysInfo::NumberOfProcessors exists
on the libv8_libplatform.a, but the linker seems to pass on it.
I fixed by defining the symbol myself though.
Thanks.
- ibon
El domingo, 30 de octubre de 2016, 0:47:22
> posted reference android_arm. Did you intend to mix both target?
>
> Rodolph
>
> On Fri, 28 Oct 2016 at 12:12 ibon tolosana > wrote:
>
>> Hi,
>>
>> after successfully cross-compiling v8 for raspberry I am getting a linker
>> error on both ubuntu16.04 and an
Hi,
after successfully cross-compiling v8 for raspberry I am getting a linker
error on both ubuntu16.04 and and CentOS 7.2.
I am getting this:
CXX(host)
/data/build/v8/out/android_arm.release/obj.host/mksnapshot/src/snapshot/mksnapshot.o
LINK(host) /data/build/v8/out/android_arm.release/mks
Works perfectly on my pi.
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 the Google Groups
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, sen
ne observation: if
> you use arm-linux-gnueabihf-gcc then the float_abi will default to hardfp.
>
> Rodolph
>
> On Mon, 24 Oct 2016 at 15:17 ibon tolosana > wrote:
>
>> Hi there,
>>
>> I am having some trouble with v8 resulting libs. I compile on ubuntu
>
Hi there,
I am having some trouble with v8 resulting libs. I compile on ubuntu linux
16.04 setting arm as target using gn.
The process works just ok, but when I try to link the 4 libs with my appon
Mac, i get:
that *tmpfile64* is an undefined symbol reference. It is referenced from
platform
33 matches
Mail list logo
