Chrome crashes with out of memory exception

[gkarthiks]

We have the OpenShift Cluster with the OpenShift Console deployed. We have multiple namespaces and one of the namespace has around ~ 170 pods.

When logged in, it's terrifically slow and hangs without any response. After a while the chrome window goes to the screen with Aw snap, something went wrong while displaying this webpage message.

If I have the Developer Tools opened, it automatically puts a break point and have a message as Paused before potential out-of-memory crash as shown below.

And the memory tab shows around 2Gi as shown in the next attachments.

Also attached the logs from the DevTools console logs.
developertools.log

[spadgett]

Thanks for the report. What version are you using and what page has the problem?

We've greatly improved performance in the next-gen console in OpenShift 4.0.

• Almost all tables in the UI now use virtual scrolling with react-virtualized, so that only items currently visible on the page are rendered.
• We've moved from AngularJS 1.x to React, which is more performant and only renders parts of the UI that have changed instead of the entire page on every update.

There is a developer preview at https://try.openshift.com/ if you want to try.

If you are running 3.11, it is also possible to deploy the 4.0 console in a separate namespace to check if you still see problems in this specific project.

[gkarthiks]

Thanks @spadgett

The version of the web-console is v3.9.51 and crashes on the overview page.

That's an awesome news. But as of now I am running with 3.9, can I still deploy the v4 in a separate namespace?

[spadgett]

That's an awesome news. But as of now I am running with 3.9, can I still deploy the v4 in a separate namespace?

I suspect the operator that manages the console will fail on 3.9, but I'm not certain. You could try

https://github.com/openshift/console-operator#running-against-a--400-cluster-min-311-recommended

cc @benjaminapetersen

[benjaminapetersen]

Yeah, it will probably not deploy on 3.9 at this point (and would demand the console live in openshift-console namespace).

[spadgett]

Closing for now since 3.9 is no longer supported and 4.x should perform much better. Let us know if you see similar issues in a 4.x console.

/close

[openshift-ci-robot]

@spadgett: Closing this issue.

Details

In response to this:

Closing for now since 3.9 is no longer supported and 4.x should perform much better. Let us know if you see similar issues in a 4.x console.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.