"High memory usage: 4.6 GB" - 3..2..1.. crash

Google Chrome is starting to slow us down.

A 48GB RAM Macbook Pro doesn’t really help anymore. When a Chrome tab approaches 5 GB in memory usage, it crashes. Tried Safari, Arc, Firefox Dev Edition, Atlas, etc etc, but got the same or a similar issue on all of them.

It’s a big app. Around 8k workflows (1k backend), 700 pages & reusable elements, 250 data types, 350 option sets, 10k App Text, and a bunch of APIs + some plugins. Got these metrics from Buildprint (which is truly awesome btw, try it if you haven’t).

Anyone got thoughts or suggestions? Thanks!

Hey @building4stripe !

The memory build up hits all of us unfortunately. There are a few things I use to try and minimize how many times I need to reload the page.

  1. Add to the url the parameter issues_off=true

This will turn off the issue tracker which can significantly reduce the overall memory usage. However you no longer will know when you mess something up so be careful.

  1. Try building with more reusable elements. The more of these you incorporate in your app the more you can spread out the bulk workflows and elements so it will consume less memory when working on those individual sections.
2 Likes

Buildprint is actually just an editor wrapper so you don’t need to open the editor :rofl:

If you DM me with your email I’ll give you edit access to help you out.

Haven’t tried disabling the issue tracker before. I’ll try that when working on low-risk stuff. Thanks for the tip! We’re already using reusable elements a lot (25 pages, 650 reusable elements).

Thanks! :folded_hands:t3: Will do.