Closed
Bug 969692
Opened 10 years ago
Closed 10 years ago
For jsreftest osx tests, a memset of 512mb is taking 4+ min to complete. This is causing failures for this suite.
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jlund, Unassigned)
References
Details
discovered by dmajor, this memset normally happens in seconds on his osx laptop and on our linux prod machines. Here is an example with added print lines: https://tbpl.mozilla.org/?tree=Try&rev=e96f1ffc9165 in the 10.6 (the failed orang) and linux opt logs for jfreftest, find: regress-617935.js around that test load file, you can see 'huge_dalloc' debug lines. These show it took multiple min for 10.6 to memset 1gb and only seconds for linux (ya, mozharness timestamps in logs FTW) Outside of our production machines, devs are reporting this only takes seconds on their own osx laptops (like our prod linux machines). Not sure if this is a hardware or software issue.
Note that we worked around this problem in bug 860254 by not poisoning huge allocations since we're going to immediately unmap them anyway. However we still got a Mac-only regression (bug 973969) from the poisoning of small allocations which may be related. Here's another experiment I sent through try: https://tbpl.mozilla.org/php/getParsedLog.php?id=34925550&tree=Try&full=1 -- Search for "huge_dalloc" and note it's only the ones on regress-617935.js that are taking so long. We have other calls to huge_dalloc elsewhere in the log and they run at "normal" speeds.
Reporter | ||
Comment 2•10 years ago
|
||
since 973969 and 860254 are resolved, I am going to close this one for now.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•6 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•