* SUMMARY Profiling the timeline a lot of time was spent inside ProfileNode computing each profile node's time information. Unfortunately this information is only used by Legacy Profiler views, and not used at all in the new Timeline view, so the computation is a complete waste. We should only compute this information if needed.
<rdar://problem/17852395>
Created attachment 235727 [details] [PATCH] Proposed Fix
Comment on attachment 235727 [details] [PATCH] Proposed Fix There is no clients if these getters! It was just over engineering of the API on my part before I added the time range computation. I see no harm keeping them as lazy getters though.
Comment on attachment 235727 [details] [PATCH] Proposed Fix Clearing flags on attachment: 235727 Committed r171787: <http://trac.webkit.org/changeset/171787>
All reviewed patches have been landed. Closing bug.