Since then, there hasn’t been a day that my editor doesn’t crash and I have to reload the page. And this happens several times a day. For example, today, I’ve been working for 1 hour and this has already happened 3 times.
Before anything else, let me make it clear that my app is indeed a complex app, but modularized, so 90% of the time I’m working on REs and not on pages full of elements. I also use a gaming laptop with 32gb of ram.
As I said, nothing was a problem before this update and I don’t believe that the problem is my computer. You know, I’m not complaining about the updates, but clearly something has changed in a way that has directly impacted the editor’s performance on our end. And if any further updates to the editor (to improve it) result in this same performance degradation, well, where do we end up?
To get a better idea, feel free to point out your case in the poll below:
freezing, and it slowing substantially is pretty common for me, but refreshing the page normally sets it right for a good while. This is mostly only a thing on v large or complex pages.
Sometimes, a single browser tab with the editor open is consuming almost 4 GB of memory. Every time I merge a branch or use the app search tool, I have to close the editor and open it again. Working with multiple tabs is almost impossible. Bubble is bubbling.
In my case I noticed recently the Issue checker is not working properly, and I am not talking about the backend workflow chek. The whole bubble platform is behaving erratic for me.
Well, this is a known issue in which in some cases it is necessary to visit a page or RE so issue checker can identify issues.
But I’ve noticed an inverse behavior, which is difficult to reproduce. It usually happens after merging some branch to main. Right after the merge, the issue checker detects issues in elements that haven’t even been changed, but if you just reload the page, these issues disappear.
I’ve also identified other case, again difficult to reproduce, in expressions that were being used in Backend Workflows or Custom Events parameters. If the parameters are removed without the expressions that fed these parameters also being removed, it may be that at some point in the future an issue will be detected, when you remove a field or option set that was part of that expression that fed the parameter, but then you now no longer have access to it because the parameter has been removed. This is a headache when it happens.
Exactly. Such a pain. Ive started using multiple browsers instead of multiple tabs which is inconvenient to switch back and forth and also annoying because copying and pasting of bubble elements and expressions doesnt work across different browsers
I’ve had the same thing here, issue checker shows nothing except when “Only search current page” is checked. Then I just keep hitting search, since issues appear one at a time when I fix an issue.
I find the editor actually works better than it has in the past. But it does get clogged up and slow quickly. The things that have helped the most for me are:
Hard resets: 1) Go to dev mode in browser (often alt+f12 or similar), 2) Hold refresh page icon, 3) “Empty cache and hard reset”
Switching browser. In my case going from Chrome to Microsoft edge actually improved performance slightly
I’m also working with complex and large apps. It also helped a lot to switch out the ram in my laptop from 32 to 64gb (but that should never have to be a requirement to run the editor haha)
near ZERO – I have a Macbook pro with 32G memory and I think that helps.
Also I mostly don’t work in US hours - and I notice the Editor (anecdotally) get slower when the US & Brazil wake up.
It does crash in some times in very very large apps. But having worked on a few hundred different Bubble apps - this is a very very large app! and I just clear the cache and reload and things are back on track.
I also use Edge, never had a crash and barely any slowdowns. The main hitch is when I first load up the site in the editor. That’s like 1 second of unresponsiveness. I also have only a small handful of extensions. 3 year old CPU and 32GB of RAM.
