Solved: Running out of memory 64 bit Chrome

Scott_P · ‎12-03-2018

Hi All,

Is anyone else having issues running out of memory on 64 bit chrome. My apps are quite data heavy, but using a lot of galleries to try to reduce the number of items per page.

Cheers,

Scott

Drrickryp · ‎12-12-2018

Hi @Scott_P,

@Anonymous asked me to comment on your issue with Chrome64. When I initially started using PowerApps I was still using the connector to my MS Access WebApps tables through it's native Sql server and I had a great improvement in performance compared with regular Chrome. When WebApps were fully deprecated, I lost that connection and had to use SharePoint. I have since migrated to CDS and have had no problems with poor performance when using any web browser. I suspect that in the end, the problem was with changes being made to take down the WebApps server.

There was a comparison done between Chrome 32 and Chrome 64 ref: http://laptoplcdrepair.net/chrome-64-bit-vs-chrome-32-bit-performance-ram-consumption-and-security/

The conclusion of the article was to quote

"Chrome 64-bit topped Chrome 32-bit in every performance test. It ends up consuming much more memory, which is something to bear in mind if you run Chrome on low-end devices (4 GB or less), although it would not be a problem in current devices with 8-16 GB.

Stability is another element to take into consideration. According to Google, the 64-bit version is twice more stable than the 32-bit version, with the former showing half the errors of the latter in most web pages."

I hope that this addresses your issue. You may want to try a different browser than Chrome because it tends to be a memory hog and if you have limited memory on the device you are using, it may be a factor. In several tests, Opera used the least amount of RAM so you may want to try that one.

View solution in original post

Drrickryp · ‎12-12-2018

Hi @Scott_P,

@Anonymous asked me to comment on your issue with Chrome64. When I initially started using PowerApps I was still using the connector to my MS Access WebApps tables through it's native Sql server and I had a great improvement in performance compared with regular Chrome. When WebApps were fully deprecated, I lost that connection and had to use SharePoint. I have since migrated to CDS and have had no problems with poor performance when using any web browser. I suspect that in the end, the problem was with changes being made to take down the WebApps server.

There was a comparison done between Chrome 32 and Chrome 64 ref: http://laptoplcdrepair.net/chrome-64-bit-vs-chrome-32-bit-performance-ram-consumption-and-security/

The conclusion of the article was to quote

"Chrome 64-bit topped Chrome 32-bit in every performance test. It ends up consuming much more memory, which is something to bear in mind if you run Chrome on low-end devices (4 GB or less), although it would not be a problem in current devices with 8-16 GB.

Stability is another element to take into consideration. According to Google, the 64-bit version is twice more stable than the 32-bit version, with the former showing half the errors of the latter in most web pages."

I hope that this addresses your issue. You may want to try a different browser than Chrome because it tends to be a memory hog and if you have limited memory on the device you are using, it may be a factor. In several tests, Opera used the least amount of RAM so you may want to try that one.

Anonymous · ‎12-12-2018

Thanks for your help @Drrickryp! @Scott_P - can you please review the reply and let us know if that helps?

@Anonymous

Scott_P · ‎12-14-2018

Apologies for the delayed repsonse. The device I am using, is not too bad in terms of peformance.

We're faced with many challenges with migrating to CDS, more specifically the connections we have set up that we rely on for our end users. Our concern is, that when we do migrate we're going to have to spend a significant amount of time setting up these connections again.

We have extremely large applications, that are doing an awful lot, and it only seems to suffer with memory issues, when we are really pushing the limitiations of what we are asking it to do.

I get that Chrome is a memory hog... but I can't be the only one who is loathed to use edge.