Bubble editor keep crashing

Bubble editor keep crashing. .
can anybody please help us . @emmanuel .
its been such a long time that editor is not working properly.
how we can solve it.


Like it says you’re out of memory.

@keith i am on personal plan and i have 10 gb storage out of 240 mb is used only.


If you’re the sort who never reboots their machine or browser, consider hitting F12 (expose console) and then right click reload and select “Clear Cache and Hard Reload” ( or similar).

@keith have tried this too .but its not working.

File a bug report if so: Support | Bubble

Hey @yash4

Out of memory it means the Memory RAM of your computer
Chrome would used a lot of memory ram especially running a Bubble Editor Application
just avoid lots of Tabs on chrome or upgrade your Memory ram 8 gb or higher
I have 8gb ram and this is the memory used on Chrome plus cached files


yes you need to free up some space in your memory on your computer. Bubble editor crashed yesterday, I had to close four tabs that I had opened and closed all other operating programs. Worked fine then.

There seems to a Bubble and/or browser limitation causing this too. My coworkers and I get these crashes when multiple Bubble Editor tabs are open despite having 64GB of physical memory and the actual usage of the browser never exceeding 5-8GB or so. The Bubble tabs will just crash with “out of memory” error.

Here is a live example. I was able to make this happen by just changing between pages, and changing between workflow/design tab in a pretty reasonable way with two editor tabs open.

You can see I am only using a peak of around 20GB of RAM in total out of 64GB, and the drop in the graph is when the tabs crash which frees up about 5GB. Clearly not actually running out of memory, unless the browsers are putting some kind of artificial limitation on how much memory each tab can use. It happens across browsers and also happens on my Macbook Pro.

1 Like

I was hitting this as well and I have your solution. This was happening to me with 16gb of memory on a $1,600 gaming computer. Chrome would literally be using 14+ GBs of memory after having Bubble open for a couple hours on 2-3 tabs.

The complexity of the pages you have open in Bubble seems to greatly effect this. I have a single page app with separate pages for mobile and desktop, so having both open (I often make edits to both in tandem) was crushing my system.

I have (mostly) fixed this now via these two approaches:

1. Disable Hardware Acceleration in Chrome’s performance settings. Seems like this would help performance, but this is only the case when watching movies or playing games in browser. For Bubble, it just puts the load on your graphics card instead of your regular memory/CPU, and your regular memory/CPU will be more capable and efficient at running Bubble.

2. Increase your PC’s paging file size. Your paging file is the portion of your hard drive set aside for use as virtual memory. So basically, if your paging file is set to 16gb, and you have 16gb of regular ram, then you have 32gb of usable memory. Paging file memory is not as fast, but your PC can use it as a backup to avoid memory related application crashes.

  • Search for “Advanced System Settings” on your computer, Open it.
  • Under “Performance” click “Settings”.
  • Go to the “Advanced” tab.
  • Under Virtual Memory, click “Change”.
  • Select custom size, and set the Min and Max size to your desired size(same value in both). Will probably need to be at least 10gb (10,000 mbs) to make Chrome + Bubble behave. I have mine set to 15,000 mbs).

It’s worth noting that a solid state hard drive greatly increases the performance of your paging file. If you have a hard “disk” rather than a SSD, this might not be as effective.

Also be aware that you are setting aside a portion of your hard drive for virtual memory, which means you are decreasing the amount storage space you have on your computer by whatever amount you set your paging file to. This is the downside to increasing the size of your paging file.

Bonus Tip:

Use reusables to extract out aspects of your single page app onto separate “pages” to allow for easier editing. This decreases the complexity of your core pages and makes them easier to edit as well. Actual end user performance concerns for your app have to take precedence over this of course, but I’ve often found that reusables (when used correctly) can increase performance both in editing and in your live app.


Thanks. I’ll give it a try - though my paging file is already set to 20GB and I have an RTX 3090 so the GPU should be pretty good at hardware acceleration as well. Page file disk is a pretty fast 2TB PCI-e 4.0 NVMe drive and again I’ve got 64GB of physical memory that is not being all used up so I shouldn’t need it.

EDIT: Still crashes with hardware acceleration off.


This topic was automatically closed after 70 days. New replies are no longer allowed.