Summary: | Rare failure in regress/script-tests/sink-huge-activation.js.ftl-eager | ||
---|---|---|---|
Product: | WebKit | Reporter: | Filip Pizlo <fpizlo> |
Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Normal | CC: | basile_clement |
Priority: | P2 | ||
Version: | Other | ||
Hardware: | All | ||
OS: | All |
Description
Filip Pizlo
2015-08-20 13:25:28 PDT
This is incredibly weird. It looks like the allocation sinking phase for some reason failed to realize the node at @53 should be sunk because it uses the activation at @17 (i.e. ObjectAllocationSinking::determineSinkCandidates failed its job). I have absolutely no idea what could have caused this, and was unable to reproduce it either. What revision did you see this in? |