[v8-dev] Re: Issue 4359 in v8: Crash in v8::internal::MemoryChunk::IsEvacuationCandidate on arm64 in mjsunit/strong/load-proxy.js

Updates: Status: Fixed Comment #4 on issue 4359 by mlippa...@chromium.org: Crash in v8::internal::MemoryChunk::IsEvacuationCandidate on arm64 in mjsunit/strong/load-proxy.js https://code.google.com/p/v8/issues/detail?id=4359 (No comment was entered for this change.) -- You

[v8-dev] Re: Issue 4359 in v8: Crash in v8::internal::MemoryChunk::IsEvacuationCandidate on arm64 in mjsunit/strong/load-proxy.js

Comment #3 on issue 4359 by bugdro...@chromium.org: Crash in v8::internal::MemoryChunk::IsEvacuationCandidate on arm64 in mjsunit/strong/load-proxy.js https://code.google.com/p/v8/issues/detail?id=4359#c3 The following revision refers to this bug:

[v8-dev] Re: Issue 4359 in v8: Crash in v8::internal::MemoryChunk::IsEvacuationCandidate on arm64 in mjsunit/strong/load-proxy.js

Updates: Status: Started Comment #2 on issue 4359 by mlippa...@chromium.org: Crash in v8::internal::MemoryChunk::IsEvacuationCandidate on arm64 in mjsunit/strong/load-proxy.js https://code.google.com/p/v8/issues/detail?id=4359 Hej Yang, This is just to let you know that I am still

[v8-dev] Re: Issue 4359 in v8: Crash in v8::internal::MemoryChunk::IsEvacuationCandidate on arm64 in mjsunit/strong/load-proxy.js

Comment #1 on issue 4359 by yang...@chromium.org: Crash in v8::internal::MemoryChunk::IsEvacuationCandidate on arm64 in mjsunit/strong/load-proxy.js https://code.google.com/p/v8/issues/detail?id=4359 This caused this CL to be reverted: