+ author from regression blame list

As a non-Googler, is there anything else I can do besides emailing inferno@chromium.org for access to the testcase link?

I'll try to minimize the test case more and then post it here. Maybe this is a non-issue with non-stable sorting.

// Just another case of non-stable sorting. Somehow the code change has flushed it out. I think there's nothing we can/should do atm. This is by design and I will think about if there's any way to suppress this in the correctness fuzzer.

// Program:
v = [];
v[40] = 'c';
v[50] = 'deleted';
delete v[50];
v[1999] = 'e';
v.sort(function() {})
print(v[0] + " " + v[1]);

// Output:
# Compared x64,ignition with ia32,ignition
#
# Flags of x64,ignition:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 1474417455 --ignition --turbo-filter=~ --hydrogen-filter=~ --validate-asm --nocrankshaft
# Flags of ia32,ignition:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 1474417455 --ignition --turbo-filter=~ --hydrogen-filter=~ --validate-asm --nocrankshaft
#
# Difference:
- c e
+ e c
#
# Source file:
none
#
### Start of configuration x64,ignition:
c e

### End of configuration x64,ignition
#
### Start of configuration ia32,ignition:
e c

### End of configuration ia32,ignition

FYI: The regression range in the report pointed to this change:
https://chromium.googlesource.com/v8/v8/+/e7b78ac22937f994d35376b38416a5844d6beced

ClusterFuzz has detected this issue as fixed in range 44025:44026.

Detailed report: https://clusterfuzz.com/testcase?key=5211430057148416

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition_turbo:ia32,ignition_turbo
  sources: 6b0
  
Sanitizer: address (ASAN)

Regressed: V8: 43016:43017
Fixed: V8: 44025:44026

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv97BjjdHsCheJgh77L1ef6uelQHH9NuJ8fplmAUOmkZqQm3I5-_DMnf8ieu8wqHoIox0YPeusZVveFYAxcQH4mZzQd7RsXGrYobUu3BauksMQqarSoZy1U56qzkaTzxYVmf9Ooohj1Hi_mpPkzCErLtgJt6jovHcAUYlJKIDv5Mf1SWpad5DrkjakZLGWC1uijpY3FMt20212vO_k9uPcZFFYgiDRK-3uXCPXVc_bERgPq6bxhlB09zIkGtMGBU6qntRBRoACxLxrLi7zPe5FJnXd_H1QEnc8hwOEx_aacb_PnSB8e8VEermojf6kxq19gKD1FVkUJ9sKIFTvk8khiVfd8mGdu7Je0SWIrWFja0amCCdC3E?testcase_id=5211430057148416


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.