I've been trying to figure out what's casuing a crash around an isolate 
being released.
On Mac OS X i was getting a bad exec in an atomic load related to 
EntryStackItem.

I moved over to windows to see if it would crash there and it does but with 
a different error.

Possibly because on widows i've updated to 12.3.219.15. I also saw the same 
thing in 11.8..173.
I elminated any of my code by copying over the hello world sample and build 
it under my project bazel build and it also crashes. However it doesn't 
crash when i added it as a build target for the project that builds the v8 
libraries for me.

That process is use the args file to build the v8 then package all the 
.objs for a specified set of of v8 libraries into a .a since bazel doesn't 
like .lib in cc_library.

Oddly enough when i run all my tests using non debug builds it has no 
porblem running just the debug builds of v8.

Currently seeing these 2 crashes

This one occurs in one of my yests when calling HasCaught of a TryCatch
#
# Fatal error in C:\Users\dorml\github\v8Dist\v8\src/objects/slots.h, line 
84
# Debug check failed: IsAligned(ptr, kSlotDataAlignment).
#
#
#
#FailureMessage Object: 000000FCC711DCA

If i comment that line out then It crashes in the HandleScope when it's 
leaving it's scope and being deleted. It crtashes on this line
  CHECK_EQ(scope_level_, i_isolate_->handle_scope_data()->level);

Since the level is 1 and not 0.
All the code was working prior to moving up to more recent releases of v8

I suspect it may be some difference in debug builds between v8 build 
process and bazel build process toolchains.

-- 
-- 
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
--- 
You received this message because you are subscribed to the Google Groups 
"v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-dev/236b55d2-1681-4bd9-8c06-d4c7b9b746e4n%40googlegroups.com.

Reply via email to