Asking the browser to render large timelines is very slow. We have a canvas implementation of the timeline that we should use instead.
Created attachment 375371 [details] Patch
Created attachment 375439 [details] Patch
Created attachment 375454 [details] Patch
Created attachment 375574 [details] Patch
Created attachment 375638 [details] Patch
Comment on attachment 375638 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=375638&action=review > Tools/resultsdbpy/resultsdbpy/view/static/js/timeline.js:368 > } Since now the element's children are multiple canvas, using element.innerHTML may cause some memory can not be gc, please use DOM.inject everywhere which will clean all the ref's reference, so that it can be gc finally. > Tools/resultsdbpy/resultsdbpy/view/static/js/timeline.js:555 > + // FIXME: We should do something sane here, but we probably need another endpoint I guess we will need a popover ? > Tools/resultsdbpy/resultsdbpy/view/templates/suite_results.html:66 > this.children = {}; Same thing around here.
unofficially r=me
Created attachment 375769 [details] Patch
Comment on attachment 375769 [details] Patch rs=me
Created attachment 375811 [details] Patch for landing
Comment on attachment 375811 [details] Patch for landing Clearing flags on attachment: 375811 Committed r248425: <https://trac.webkit.org/changeset/248425>
All reviewed patches have been landed. Closing bug.
<rdar://problem/54086870>