-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FATAL ERROR: v8::Object::GetAlignedPointerFromInternalField() Internal field out of bounds #48114
Comments
That likely originates from here (aside: that reinterpret_cast should probably be static_cast): Line 246 in 92a938b
Which in turn calls this method: Lines 93 to 98 in 92a938b
Is it an option for you to apply this patch and build from source? Please try repeatedly to see if the slot count is always the same or not. diff --git a/src/base_object-inl.h b/src/base_object-inl.h
index feaeab306ac..4f2895b4d3e 100644
--- a/src/base_object-inl.h
+++ b/src/base_object-inl.h
@@ -92,7 +92,7 @@ void BaseObject::SetInternalFields(v8::Local<v8::Object> object, void* slot) {
BaseObject* BaseObject::FromJSObject(v8::Local<v8::Value> value) {
v8::Local<v8::Object> obj = value.As<v8::Object>();
- DCHECK_GE(obj->InternalFieldCount(), BaseObject::kInternalFieldCount);
+ CHECK_GE(obj->InternalFieldCount(), BaseObject::kInternalFieldCount);
return static_cast<BaseObject*>(
obj->GetAlignedPointerFromInternalField(BaseObject::kSlot));
} |
@bnoordhuis So, after doing a debug build from source with the patch. The process seems to consistently crash (when it crashes at all) at that location. We also tried running it through lldb, the program halted at the following stack trace. I'm not sure if it is related.
|
@fd what message does the assertion print? Is it always the same one? |
Version
v20.2.0
Platform
Darwin foo.local 22.4.0 Darwin Kernel Version 22.4.0: Mon Mar 6 21:01:02 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T8112 arm64
Subsystem
No response
What steps will reproduce the bug?
No idea.
This is code I can not share and I don't understand the issue, so I can't create a reproduction.
I am fully aware how useful it is to have reproducible bug, but I really can not provide a reproduction in this case.
I will check internally if the code in question can be made open source so that I can share it.
How often does it reproduce? Is there a required condition?
Intermittent.
Some runs work, others do not.
What is the expected behavior? Why is that the expected behavior?
No Fatal error, segfaults or bus error
What do you see instead?
These errors never happened before on node 18 or lower :
Additional information
This is related to
WASI
The text was updated successfully, but these errors were encountered: