Intermittent Win64 PGO test_bug732665.xul | Chrome should be able to have at least 10 heavy frames more stack than content: 57, 48 | Chrome should be invokable from content script with an exhausted stack: 9

RESOLVED FIXED in Firefox 40

Status

()

defect
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: RyanVM, Assigned: shu)

Tracking

({intermittent-failure})

Trunk
mozilla40
x86_64
Windows
Points:
---

Firefox Tracking Flags

(firefox38 unaffected, firefox39 unaffected, firefox40 fixed, firefox-esr31 unaffected, firefox-esr38 unaffected)

Details

Attachments

(1 attachment)

+++ This bug was initially created as a clone of Bug #1157415 +++

*cry*

08:52:25 INFO - 1892 INFO TEST-START | js/xpconnect/tests/chrome/test_bug732665.xul
08:52:25 INFO - 1893 INFO TEST-UNEXPECTED-FAIL | js/xpconnect/tests/chrome/test_bug732665.xul | Chrome should be able to have at least 10 heavy frames more stack than content: 57, 48 - expected PASS
08:52:25 INFO - 1894 INFO TEST-UNEXPECTED-FAIL | js/xpconnect/tests/chrome/test_bug732665.xul | Chrome should be invokable from content script with an exhausted stack: 9 - expected PASS
08:52:25 INFO - MEMORY STAT vsize after test: 1065144320
08:52:25 INFO - MEMORY STAT vsizeMaxContiguous after test: 8562047393792
08:52:25 INFO - MEMORY STAT residentFast after test: 399241216
08:52:25 INFO - MEMORY STAT heapAllocated after test: 134400254
08:52:25 INFO - 1895 INFO TEST-OK | js/xpconnect/tests/chrome/test_bug732665.xul | took 47ms
Flags: needinfo?(shu)
Unending torments.
Try for tweaking stack limit for win64:

https://treeherder.mozilla.org/#/jobs?repo=try&revision=fc2f4151d607
Flags: needinfo?(shu)
Ugh, forgot to make it a PGO build. New try:

https://treeherder.mozilla.org/#/jobs?repo=try&revision=5acbbf6e3edd
Attachment #8602568 - Flags: review?(bobbyholley)
Attachment #8602568 - Flags: review?(bobbyholley) → review+
https://hg.mozilla.org/mozilla-central/rev/98f15494f0d4
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla40
You need to log in before you can comment on or make changes to this bug.