Closed Bug 1387263 Opened 7 years ago Closed 7 years ago

Intermittent js/src/jit-test/tests/basic/testBug756919.js | js/src/jit-test/tests/basic/testBug756919.js:3:1 Error: attempt to set maxBytes to the value less than the current gcBytes (1212416) (code 3, args "--baseline-eager")

Categories

(Core :: JavaScript: GC, defect, P5)

defect

Tracking

()

RESOLVED FIXED
mozilla57
Tracking Status
firefox56 ? fixed
firefox57 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: jonco)

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

[Tracking Requested - why for this release]: Nearly permafailing test.

Jon, this has been nearly permafail since 56 was merged to Beta on Wednesday (1 green run out of 6 attempts). Can you please take a look?
Flags: needinfo?(jcoppeard)
Flags: needinfo?(jcoppeard)
Attached patch bug1387263Splinter Review
This is a race condition setting maxBytes although I can't see exactly how it can happen.  The failures are all with --baseline-eager so I guess compilation is allocating something in the background although I'm not sure of the details.  I can't reproduce this locally.

I rewrote the testcase to use oomTest rather than setting maxBytes.  That should fix this.
Assignee: nobody → jcoppeard
Attachment #8893746 - Flags: review?(jdemooij)
Attachment #8893746 - Flags: review?(jdemooij) → review+
Pushed by jcoppeard@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/95e88f20301e
Rewrite test case to remove possible race condition r=jandem
https://hg.mozilla.org/mozilla-central/rev/95e88f20301e
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla57
Whiteboard: [checkin-needed-beta]
You need to log in before you can comment on or make changes to this bug.