-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Corruption detected by heap verifier #60552
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
Comments
The null object and some following objects get corrupted when Array::NewUninitialized sees Object::Allocate return null.
|
copybara-service bot
pushed a commit
that referenced
this issue
Apr 16, 2025
TEST=vm/cc/VMIsolateImmutability Bug: #60552 Change-Id: I5a51718996ce735a67c73500c46f0e7cc16f654a Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/422901 Commit-Queue: Ryan Macnak <[email protected]> Reviewed-by: Siva Annamalai <[email protected]>
copybara-service bot
pushed a commit
that referenced
this issue
Apr 16, 2025
Array::New[Uninitialized] don't expect to get null from Object::Allocate. Using longjmp seems more robust than adding checks everywhere. TEST=vm/dart/gc/scavenger_abort_test Bug: #60552 Change-Id: I2750427c41751f8306d5c8dc28afaf052b6e9d74 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/422902 Commit-Queue: Ryan Macnak <[email protected]> Reviewed-by: Alexander Aprelev <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
log
The text was updated successfully, but these errors were encountered: