Hot Fix: Editor Crashing Constantly - Here's How To Resolve!

Tips
1

The bubble editor has been progressively getting slower and buggier. I recently had the painful experience of having to update a huge bubble app that had been built very poorly (good ideas but bad implementation). The app itself has 50+ pages and 100+ reuseable elements and 100+ datatypes and it is huge.

The problem I quickly came across was that the bubble editor would constantly crash every 30 minutes or so, sometimes every 5 minutes on particularly heavy pages. It would noticeable slow down to a crawl as I jumped through the pages. After a quick look in the chrome stats I could see why - the bubble editor is trying to store everything in the local cache.

Unfortunately this means that if you jump from one complex page to another all the previous pages junk is still stored in the cache locally. Basically with every load of new data you put another straw on the camels back until eventually it crashes due to “running out of memory”.

The solution however is actually very simple. All we need to do is clear the cache - clear the camels back.

Simply refreshing the tab does not work - the cache is not cleared.
Changing browsers works only until the cache is clogged up again.
Restarting the browser may work if you have the settings set to clear the cache on restart, but if you check the windows task manager you’ll notice that most browsers never truly restart fully - they keep running in the background even when closed.
So restarting the computer or killing the browser in the task manager is what we are left with.

BUT, there is a better way.

Essentially all we need to do is do a hard refresh on the tab to clear the cache. You can do this in chrome by holding Ctrl when you click the refresh button.

But an even better way is to use a chrome plugin - I’ve been using “auto refresh plus” for the past two weeks and the bubble editor has never crashed since!

So far the optimal settings are to do a hard refresh on all dev tabs every 30 minutes. You can even set the plugin to autostart on bubble editor pages.

I’ve been incredibly frustrated by this issue for months and it seems to only be getting worse and worse with each bubble “update” but now I can actually use the editor without yelling at it constantly when it crashes.

Anyway, I know there are a lot of forum topics on this subject (I read them alll trying to solve the problem!). Hopefully this solves the issue for you as well.

11 Likes
2

This is interesting to know and thanks for sharing this. So is this just going from one page to another or even the “undo/redo” history that causes this?

If it is caused by just going from one page to another, then it is really bad that Bubble is having it, as history of pages has been a pretty useless thing (at least for me). Whenever I tried to go back in the browser it has not really worked well and I simply select the page again even if I want to back to the page I was on.

In fact if that feature causes so much of memory issues that we are dealing with, then they should probably remove this feature or put it only for those who really want. I will be happy if the editor is not crashing and crawling even if it doesn’t store page history.

Maybe you could take this up with Bubble and suggest them this? They don’t need to issue hacks like passing url parameters to make issue checker off.

3

thanks it´s happening to me will try that

4

That’s interesting, thanks for sharing!

5

It works! Thanks a lot. I used to refresh my browser every hour.

6

The issue extends beyond the issue checker and comes mostly from having to load all the elements and logic on the page loads of the editor.

However, if you have more than 100 issues I’ve noticed a very steep decline in performance - it seems like the issues are stacked into the local cache and are particularly heavy on resources.

Turning the issue checker off can be done with the url parameter but it doesn’t resolve the underlying problem. Having the issue checker off is quite annoying as well because when you turn it back on you might find you’ve created 100+ issues by changing something and then the app can get very slow as you try to fix the issues - whereas leaving it on and fixing issues as they come up is more performant.