[Heap] Allow UncompiledDataWithoutPreParsedScope in LO space.
Bytecode flushing can overwrite a bytecode array with an UncompiledDataWithoutPreParsedScope. Since the bytecode array could be in the LO space, then we also need to allow UncompiledDataWithoutPreParsedScope in the LO space if it has overwritten a large bytecode array. BUG=v8:8395 Change-Id: I1b83b5c7a61830f5576260a4f4f4c0b689818acc Reviewed-on: https://chromium-review.googlesource.com/c/1373775 Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#58186}
This commit is contained in:
parent
4e5008a50d
commit
9ec7e04ddc
@ -3642,7 +3642,8 @@ void LargeObjectSpace::Verify(Isolate* isolate) {
|
||||
object->IsPropertyArray() || object->IsByteArray() ||
|
||||
object->IsFeedbackVector() || object->IsBigInt() ||
|
||||
object->IsFreeSpace() || object->IsFeedbackMetadata() ||
|
||||
object->IsContext());
|
||||
object->IsContext() ||
|
||||
object->IsUncompiledDataWithoutPreParsedScope());
|
||||
|
||||
// The object itself should look OK.
|
||||
object->ObjectVerify(isolate);
|
||||
|
Loading…
Reference in New Issue
Block a user