Bug 181227

Summary: [MIPS] JSC test failure: stress/new-largeish-contiguous-array-with-size.js
Product: WebKit Reporter: Guillaume Emont <guijemont>
Component: JavaScriptCoreAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: aperez, dominik.infuehr, glore, guijemont, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Description Guillaume Emont 2018-01-02 16:13:30 PST
This failure happens about every 2-3 runs on the MIPS buildbot. We see:

  stress/new-largeish-contiguous-array-with-size.js.ram-size-10000000: Exception: Error: heap too big after forced GC: 1368418

Locally, I can reproduce and get a different value:

  # i=1; while jsc --forceRAMSize=10000000 JSTests/stress/new-largeish-contiguous-array-with-size.js ; do echo $i; i=$((i+1)); done
  1
  2
  Exception: Error: heap too big after forced GC: 1355035
Comment 1 Guillaume Emont 2018-01-02 16:15:09 PST
It is unclear to me whether this is a sign of a bug or that the test needs to check against a higher maximum.
Comment 2 Guillaume Emont 2018-01-02 16:51:31 PST
It looks like on different runs, I get one of the following progression of heap sizes:
 - 3359463 before GC and 158823 after GC
 - 3359495 before GC and 158855 after GC
 - 2159159 before GC and 558839 after GC
 - 1759047 before GC and 958887 after GC
 - 2559143 before GC and 1358903 after GC (failing the test)

For some of them, I get slight variations with the last 2 digits being different.
Comment 3 Guillaume Emont 2021-06-24 09:58:11 PDT
*** Bug 227356 has been marked as a duplicate of this bug. ***
Comment 4 Geza Lore 2022-02-16 03:49:42 PST
Created attachment 452174 [details]
Patch
Comment 5 EWS 2022-02-16 06:46:49 PST
Committed r289889 (247327@main): <https://commits.webkit.org/247327@main>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 452174 [details].
Comment 6 Radar WebKit Bug Importer 2022-02-16 06:47:59 PST
<rdar://problem/89022920>