v8-users@googlegroups.com

2020-06-17 Thread Immanuel Haffner
Hey Dan, thanks for the quick reply. I figured that this is related to pointer compression. I *enabled* pointer compression and the leak is gone. Regards, Immanuel delp...@chromium.org schrieb am Mittwoch, 17. Juni 2020 um 15:03:25 UTC+2: > Thanks for the report. This may be a bogus report (

v8-users@googlegroups.com

2020-06-17 Thread Dan Elphick
Thanks for the report. This may be a bogus report (in that the memory isn't actually leaked) because we use mmap to allocate our memory for MemoryChunks, which means LeakSanitiser doesn't see that there is a connection to the memory pointed to by the MemoryChunk. Alternatively I've created a real l

[v8-users] Re: Failed to cross compile v8 for iOS: error: unknown directive .type PushAllRegistersAndIterateStack

2020-06-17 Thread kosit la-orngsri
เมื่อ วันศุกร์ที่ 8 พฤษภาคม ค.ศ. 2020 20 นาฬิกา 18 นาที 35 วินาที UTC+7, 许超前 เขียนว่า: > > $ ninja -C out/ios.release > > ninja: Entering directory `out/ios.release' > > [195/2128] CXX obj/cppgc_base/push_registers_asm.o > > FAILED: obj/cppgc_base/push_registers_asm.o > > clang++ -MMD -MF obj/c

v8-users@googlegroups.com

2020-06-17 Thread Immanuel Haffner
I create an instance with v8::Isolate::CreateParams create_params; create_params.array_buffer_allocator = allocator_ = v8::ArrayBuffer::Allocator::NewDefaultAllocator(); isolate_ = v8::Isolate::New(create_params); and dispose of it with isolate_->Dispose(); delete allocator_

v8-users@googlegroups.com

2020-06-17 Thread Immanuel Haffner
Build args are is_clang=true is_component_build=false v8_monolithic=true v8_enable_pointer_compression=false treat_warnings_as_errors=false v8_use_external_startup_data=false use_sysroot=false use_custom_libcxx=false clang_use_chrome_plugins=false target_cpu="x64" is_debug=true use_debug_fissi

v8-users@googlegroups.com

2020-06-17 Thread Immanuel Haffner
Hi all, after upgrading to v8.5.183 the LeakSanitizer of clang detects a memory leak in embedded V8: ==145652==ERROR: LeakSanitizer: detected memory leaks Direct leak of 12300 byte(s) in 3 object(s) allocated from: #0 0x562b902d2ff1 in calloc (/home/immanuel/Documents/Work/PhD/mutable/muta

Re: [v8-users] Re: Compile Error with `use_custom_libcxx=false`

2020-06-17 Thread 'Clemens Backes' via v8-users
On Wed, Jun 17, 2020 at 10:47 AM Immanuel Haffner < haffner.imman...@gmail.com> wrote: > > Out of curiosity: wouldn't it make sense to add a CI job for > `use_custom_libcxx=false`? I guess we wouldn't need one bot for that, but as many as there are combinations of compilers and standard library

Re: [v8-users] Re: Compile Error with `use_custom_libcxx=false`

2020-06-17 Thread 'Clemens Backes' via v8-users
On Wed, Jun 17, 2020 at 10:41 AM Immanuel Haffner < haffner.imman...@gmail.com> wrote: > Hi Clemens, > > the patch is working. Thanks a lot for the quick response :) When will > this be available upstream? > The patch was merged to ToT about half an hour ago, so it should be available to you now.

[v8-users] Re: Compile Error with `use_custom_libcxx=false`

2020-06-17 Thread kosit la-orngsri
ถ้าไม่ขัดกันกับการเชื่อมโยงมันก็ดี เมื่อ วันพุธที่ 17 มิถุนายน ค.ศ. 2020 14 นาฬิกา 37 นาที 04 วินาที UTC+7, Immanuel Haffner เขียนว่า: > > I am trying to compile V8 in debug with the following build args: > > is_clang=true is_component_build=false v8_monolithic=true > treat_warnings_as_error

[v8-users] Re: Compile Error with `use_custom_libcxx=false`

2020-06-17 Thread kosit la-orngsri
เมื่อ วันพุธที่ 17 มิถุนายน ค.ศ. 2020 14 นาฬิกา 37 นาที 04 วินาที UTC+7, Immanuel Haffner เขียนว่า: > > I am trying to compile V8 in debug with the following build args: > > is_clang=true is_component_build=false v8_monolithic=true > treat_warnings_as_errors=false v8_use_external_startup_da

Re: [v8-users] Re: Compile Error with `use_custom_libcxx=false`

2020-06-17 Thread Immanuel Haffner
Out of curiosity: wouldn't it make sense to add a CI job for `use_custom_libcxx=false`? Immanuel Haffner schrieb am Mittwoch, 17. Juni 2020 um 10:41:13 UTC+2: > Hi Clemens, > > the patch is working. Thanks a lot for the quick response :) When will > this be available upstream? > > Kind regards,

Re: [v8-users] Re: Compile Error with `use_custom_libcxx=false`

2020-06-17 Thread Immanuel Haffner
Hi Clemens, the patch is working. Thanks a lot for the quick response :) When will this be available upstream? Kind regards, Immanuel Clemens Backes schrieb am Mittwoch, 17. Juni 2020 um 09:47:38 UTC+2: > Thanks for reporting this, Immanuel! > > I uploaded a fix to include : https://crrev.com/

Re: [v8-users] Re: Compile Error with `use_custom_libcxx=false`

2020-06-17 Thread 'Clemens Backes' via v8-users
Thanks for reporting this, Immanuel! I uploaded a fix to include : https://crrev.com/c/2248196 Can you check whether this also fixes the issue in your configuration? Thanks, Clemens On Wed, Jun 17, 2020 at 9:38 AM Immanuel Haffner wrote: > Oh, i forgot to mention the version. I am trying to co

[v8-users] Re: Compile Error with `use_custom_libcxx=false`

2020-06-17 Thread Immanuel Haffner
Oh, i forgot to mention the version. I am trying to compile V8 v8.5.183. But the error occurs also in older versions and is likely related to the update of the standard library rather then an update to V8. Immanuel Haffner schrieb am Mittwoch, 17. Juni 2020 um 09:37:04 UTC+2: > I am trying to c

[v8-users] Compile Error with `use_custom_libcxx=false`

2020-06-17 Thread Immanuel Haffner
I am trying to compile V8 in debug with the following build args: is_clang=true is_component_build=false v8_monolithic=true treat_warnings_as_errors=false v8_use_external_startup_data=false use_sysroot=false use_custom_libcxx=false clang_use_chrome_plugins=false target_cpu="x64" is_debug=t