Seems to be related to or duplicate of 707580.

Very likely duplicate. Smaller repro (observable between x64 and ia32 or arm):

count = 0;
(-2147483648).hasOwnProperty({
  valueOf: function() {
    count += 1;
  },
  toString: null
});
print(count);

// 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 732681078 --ignition --turbo-filter=~ --hydrogen-filter=~ --noopt
# Flags of ia32,ignition:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 732681078 --ignition --turbo-filter=~ --hydrogen-filter=~ --noopt
#
# Difference:
- 0
+ 1
#
### Start of configuration x64,ignition:
0

### End of configuration x64,ignition
#
### Start of configuration ia32,ignition:
1

### End of configuration ia32,ignition

ClusterFuzz has detected this issue as fixed in range 45789:45790.

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:arm,ignition
  sources: f99
  
Sanitizer: address (ASAN)

Regressed: V8: 43152:43153
Fixed: V8: 45789:45790

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5863375321169920


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.