Plots don't render on Chrome with a large data set (>600MB)

[shefalijoshi]

Summary

When trying to plot an extremely large dataset (with no mixmaxing), the data transferred over the network overwhelms the browser. You will inevitably reach a point where the browser runs out of memory and errors. There is different behavior in different browsers.

Chrome: Data array in memory grows and grows and grows, until Chrome has had enough, and will drop the data from memory silently.

Firefox: Data array in memory grows and grows and grows, until FF has had enough, and will throw a console error.

Expected vs Current Behavior

At the very least the user should understand that the plot is not going to render for a data set that large.

Steps to Reproduce

Environment

• Open MCT Version:
• Deployment Type:
• OS:
• Browser:

Impact Check List

• Data loss or misrepresented data?
• Regression? Did this used to work or has it always been broken?
• Is there a workaround available?
• Does this impact a critical component?
• Is this just a visual bug with no functional impact?
• Does this block the execution of e2e tests?
• Does this have an impact on Performance?

Additional Information

[davetsay]

@unlikelyzero , added a summary of what we were seeing

[davetsay]

performance.measureUserAgentSpecificMemory

[JonanOribe]

Maybe one first step here it's to show an alert pop-up to the user about what is happening. Then, second step looks for a way to deal with those load volumes.