Back to not being able to save, and constant errors. Now stuck in a loop where it exits the editor and redirects to bubble.is.
same isssue
Yep, I’m getting the same issues. I just got off “day work” and was ready to settle into some Bubblin’ action. Hope we can get someone from Bubble to weigh in here.
Same thing happening to me now
Same issue currently. Not being able to save then temporary errors kick me to bubble.is/home.
Same issue - first showing me ran into temporary bug and reloading again. Not able to edit anything.
While I was writing this - the editor started to work. Still reporting to know that this issue happened.
What exactly is influencing the editor performance? Where would the biggest gains be at to fix ourselves?
app’s plan server capacity?
Bubble server capacity?
General traffic to/from AWS us west 2 server?
editor’s current page elements amount?
editor’s current page workflows amount?
computer hardware? (what are optimal specs?)
I experienced for the first time that the editor/page ran into a bug and it actually threw me out of the editor to my apps overview page.
I reported a bug, and just got a mail saying they’ve pushed a fix. Things seem back to normal for me now.
Interestingly, hardware doesn’t always seem too much of an issue.
For example I regularly run the editor on a Chromebook with just a Intel Celeron 2.16 GHz and 2 GB Ram.
How big are the pages you are editing? Are you close to the AWS server? Are you on dedicated?
Some are pretty big. Am in the UK, so quite a way. Not dedicated.
Pretty similar to my situation. Would be interesting to pinpoint this slowness because it is hampering production quite a bit…
I’m completely out again, and status shows a response time of 6 seconds. Anyone else having trouble?
Yup, all ground to a halt again here. Just editor and development, live is working ok.
Hi,
I’m not sure if this helps but just in case…
I too experience slow downs with the Editor as my day goes. I noticed that the windows Task Manager shows that the machine’s memory allocated to the Chrome used for the Bubble Editor goes from 200MB from when I start to almost 3 GB. By the 2GB mark the experience is unbearable and my quick and dirty solution is to close the browser and reopen it.
Thanks.
Yes, there is something leaky about the editor, that is for sure.
But this is not about memory, as it slows down the dev server too and closing the browser makes no difference.
Same here… Editor has some memory leakage issue for sure… Goes up to 2-3gb if open for a while.
I’m happy with 2GB to be honest. I’ve noticed Firefox is the most effective with memory but when it goes to 5 I need to refresh the browser. Above 5 is unusable.
Unfortunately, I don’t always want to refresh because of the loss of undo’s 
I noticed that when I start a whole new app, everything is for the most part super quick. But an empty page in my main app is already pretty slow. So other stuff also makes the editor slow, not stuff that is present on the current page.
Perhaps a combination of. a lot of pages plugins or?
Maybe Bubble could be more effective when it comes to loading data in the editor?
We also had issues end of week with editor being painstakingly slow! Each click taking several seconds to respond in the editor. From an efficiency standpoint it doesn`t help much with rapid-app tool like bubble when it is so slow to work in it. We gotta find a way to fix this asap, we are losing developer progress by the day the editor is like this.
Anyone up for crowdfunding some performance analysis of both the editor, as well as the front-end of some large single-page apps?
Would be good to get a really experienced chrome developer tools guy to look at:
- Network requests. (noticed quick time to first byte response, but long content-download. For a simple no data response. This means more probably that the server operation is slow, assuming the network connection is good.)
- Memory leaks and memory management. (bubble editor roaming 1-2gb at times.) (Even end user bubble app using 1gb at times.)
- Function performance. (We would have to send which functions are slow, back to bubble since they are anonymized and bubble has the source-map to see which functions are not working well.
If we cant bankroll it. Any devs in here with experience with the Chrome Developer tools for performance analysis?
If not feel free to learn: https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/