[v8-users] Windows x86 with stdcall?

Greetings! By adding the /Gz compiler switch and making a few minor tweaks, we've managed to build the V8 monolith with stdcall as the default convention. Unfortunately, this build doesn't work. We can initialize V8 and spin up an isolate, but context creation crashes without a useful stack

Re: [v8-users] Issues with preserve_most?

day, February 21, 2023 at 11:12:52 AM UTC-5 clem...@google.com wrote: > On Wed, Feb 8, 2023 at 6:05 PM ClearScript Developers < > clearsc...@gmail.com> wrote: > >> Hi Clemens, >> >> >Which toolchain do you use where you see crashes? >> >> Our hack to reta

Re: [v8-users] Issues with preserve_most?

lang anyway, and I > didn't find any relevant fixes since the introduction in 2016. Which > toolchain do you use where you see crashes? Maybe we can restrict it > further to the most recent clang versions. > > On Wed, Feb 8, 2023 at 7:25 AM Jakob Gruber wrote: > >> +cle.

[v8-users] Issues with preserve_most?

Greetings! We've noticed that preserve_most was disabled for Windows/arm64 on the 11.1 branch tip today. We'd actually been struggling with extreme instability in 11.1 release builds on Linux x64, so we

[v8-users] 10.6: No public v8::PageAllocator implementation?

Our embedder has a custom v8::Platform implementation. In V8 10.6, the v8::Platform::GetPageAllocator method is abstract, and no information is provided about how to implement it. We're currently delegating GetPageAllocator to an instance of the default platform (created via

Re: [v8-users] Cross-context object usage

Thanks, Jakob. It would appear that an object's creation context indicates "which NativeContext initiated a certain action. V8 needs that information for security checks." Is that correct? An object's creation context is used for security checks? Is there no other significance to it? (And

[v8-users] Cross-context object usage

Greetings! Can someone confirm that a V8 object can be used safely across contexts within the same isolate? A related question: What is the significance of an object's creation context? Also, why don't contexts within the same isolate share built-ins such as Math et al? Thanks in advance!

Re: [v8-users] v8::Platform::PostJob and v8::platform::NewDefaultJobHandle

Great! Thanks, Clemens! On Wednesday, September 23, 2020 at 10:44:52 AM UTC-4 Clemens Backes wrote: > That is supposed to work, yes. All the DefaultJobHandle does is posting > tasks to the platform. > > On Wed, Sep 23, 2020 at 4:37 PM ClearScript Developers < > clearsc..

[v8-users] v8::Platform::PostJob and v8::platform::NewDefaultJobHandle

Greetings! We're updating our embedder for V8 8.6, and apparently our v8::Platform implementation now has to implement the new method PostJob. The comments in the header file suggest delegating the implementation to v8::platform::NewDefaultJobHandle. Our question: Is NewDefaultJobHandle safe

[v8-users] Pointer compression seemingly responsible for large memory leak

Greetings! Our project is a V8 embedding library for .NET on Windows. We have a test that spins up a context, runs SunSpider, and destroys the isolate. We run it in a loop to check for memory leaks. This test showed a dramatic leak with V8 8.0 that wasn't there with 7.9. Our tools found

Re: [v8-users] Re: Building v8 shared library on windows

Unfortunately this issue transcends export naming. V8 seems to be embracing STL data types all over its API. By sheer luck std::unique_ptr is likely to work across STL implementations (at least when used without a stateful deleter), but other data types aren't so lucky. V8 already has a bunch

Re: [v8-users] Repeated module evaluation.

be for V8 to throw an exception when an imported module has already been evaluated in a different context. On Thursday, June 20, 2019 at 1:28:14 PM UTC-4, Adam Klein wrote: > > On Wed, Jun 19, 2019 at 9:27 PM ClearScript Developers < > clearsc...@gmail.com > wrote: > >> &quo

Re: [v8-users] Repeated module evaluation.

tantiation > <https://cs.chromium.org/chromium/src/v8/include/v8.h?rcl=ab5fb228bcaf387cc72dfd93cdc62c1db4867ebf=1302> > > is tying a v8::Module to a v8::Context. So if you instantatiate a module in > multiple context, multiple evaluations should still work. > > On Thu, Jun 13

Re: [v8-users] Repeated module evaluation.

Sorry to revive this thread, but we're encountering the same issue. v8::Script is not a replacement for v8::Module; for one thing, scripts can't import modules :) In any case, V8's API seems deficient here. Modules can be imported specifically for their side effects. There's even unique syntax