[jira] [Updated] (AURORA-1345) Update status page for large jobs is killed by Chrome

["Joshua Cohen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AURORA-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Cohen updated AURORA-1345:
---------------------------------
    Description: 
When I say "killed by Chrome" I mean if left open long enough the page turns into the Chrome "Aw Snap" page.

This is presumably due to the continued addition of instance events to the page causing it to OOM and Chrome to kill it. One suggestion made to me by those more familiar with Angular was to add {{track by}} to the {{ng-repeat}} used to build the DOM for the instance events.

  was:
When I say "killed by Chrome" I mean if left open long enough the page turns into the Chrome "Aw Snap" page.

This is presumably due to the continued addition of instance events to the page causing it to OOM and Chrome to kill it. One suggestion made to me by those more familiar with Angular was to add {{track by}} to the {{ng-each}} used to build the DOM for the instance events.


> Update status page for large jobs is killed by Chrome
> -----------------------------------------------------
>
>                 Key: AURORA-1345
>                 URL: https://issues.apache.org/jira/browse/AURORA-1345
>             Project: Aurora
>          Issue Type: Bug
>          Components: UI
>            Reporter: Joshua Cohen
>
> When I say "killed by Chrome" I mean if left open long enough the page turns into the Chrome "Aw Snap" page.
> This is presumably due to the continued addition of instance events to the page causing it to OOM and Chrome to kill it. One suggestion made to me by those more familiar with Angular was to add {{track by}} to the {{ng-repeat}} used to build the DOM for the instance events.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)