Come on man, if you have a huge app you already know the answer to that 
3 Likes
Figured out the issue was a Chrome plugin. There were a few I uninstalled, so not sure which, but they were: AtomicFusion, AirDev, and Bubble Essentials. Three plugins intended to augment Editor capabilities, deliver elements, etc.
Change to the ARC browser. It clears the memory automatically before bubble crashes the tab…
Only way I’ve been able to fix bubbles memory issue in big apps.
2 Likes
Similar to @flowtron, I really like the direction in which this is going, but there are a few things that can be improved.
- As many pointed out - opening that dropdown is super slow right now. It takes about a second for me.
- It sometimes randomly scrolls to the top.
- When searching for something - it doesn’t search for the folders. Sometimes, especially in large apps, I can’t remember how exactly I named my reusable, but I know the name of the folder. I.e. we have a “Products” module, and it has an admin products reusable, a customer facing products reusable, a huge number of repeating group cells as reusables, etc etc. I want to search for the folder and then see (remember) what reusable I actually need.
- When creating a new page, reusable, etc I would like to straightaway add it to a folder:
- Drag and drop to organise everything into folders.
- As I was adding pages and reusables into folders I noticed that as you click on the three dots for the second time, after already adding a folder, the dropdown would disappear and you’ll need to click on the three dots again. Loom.
- Add ability to create a folder from this modal:
2 Likes
This is awesome. Thank you! 
Yeah definitely ARC browser helps for the memory usage, even if uses a tad more power draw, but I’ve still had about 5 crashes in the last 2 days.
I seem to get a blank white screen all of a sudden, assuming its memory related issue, this is on a single editor as well so no memory leak to consider and the only fix is a refresh to get back on track.
Definitely seemed that this update has played a factor in this 
1 Like
Well done. A clear visual improvement.
- Some issues with text breaklines
- We still need the preview to exclude the debug mode by default. Add a new mode called “Debug” after Normal.
- There need to be a “close button” on the page list dropdown. It feels wrong having to click and select an element in the editor to close it. Or at least change the arrow thing |< to a X.
- Kill the sliding pane thing. It needs to follow the newly redesign. You are probably already working on that
- Deploy confirmation box need to be hideable. Annoying when deploying changes often in the initial design phases.
- Deployment description needs to be option. Its an annoying extra click. Add a auto text like “[date] - [last change to the app from undo] - [user]” if its not filled with custom text.
2 Likes
Been my world for a long time. Also on a huge app. Multi crashes per day. Gotten used to it already. Very sadly.
Unfortunately after some thought, it’s not just that I’m not used to it. I often organize app pages by prefix, e.g. admin_PAGENAME for admin-specific pages, test_PAGENAME for test pages, zPAGENAME for pages that are unused but can’t be deleted yet.
Unfortunately, this new update makes these pages spread out all over the place. Previously, they were clustered together, so I could just scroll to the section I needed and go from there. So yes, this is just objectively a worse UX for my use case. That being said, it may not be typical.
I run a computer with 16GB ram. The editor has been incredibly slow for at least 6 months now, causing me to routinely have to restart the browser just to get it not to lag for 5 seconds (or fail to load entirely). It’s kind of just the reality we live in now; this has been reported by many people and the team has pushed forward with the editor changes regardless.
I support the idea of continuous improvement and appreciate all the efforts Bubble has made in recent months. However, it seems that we still have some problems with prior testing not being performed internally before launching some new things and, most importantly, without the option to activate/deactivate these changes as “beta features”.
This possibility was given in the updates to the new workflows tab and it was commendable. Those who wanted to opt to use it knew that it was something new and it was being improved (so there would be possible bugs), while those who didn’t want to, remained without any headaches. I think that was interesting and allowed users to choose whether to test it or not. Maybe this should be a model to be followed for most future updates.
Well, I think my role here is not only to say how powerful Bubble is, the possible opportunities it offers to people around the world and how it can change the lives of many, but also to help improve the tool with a view to benefiting the community as a whole, after all, I am part of it.
So here is my view on this new update, the view of someone who uses Bubble daily, every single day. Maybe I am not seeing many comments here or even in previous updates because most people here maybe use Bubble infrequently? Maybe because they are too lazy to report these issues while waiting for others to report them? Maybe because they are course sellers or content creators who don’t really need these small “Quality of Life” improvements (few more QoL reported here) that positively affect the productivity of those who spend their days developing in Bubble? Maybe because they use Bubble just for “fun” or personal projects that they never took forward? Maybe because they manage an agency and don’t care about the working conditions of their employees, as long as they deliver things on time? Well, I don’t know which is the case… anyway, here’s my contribution.
Issues and possible improvements that I noticed in this new version.
1 – Everything is slower: Everything seems slower in the editor when we open this section of pages and Reusable Elements (REs), including a huge delay to open this section.
2 – Absence of category separators: There is no longer a separation between pages and REs. Although both have specific icons for this purpose, the lack of a more obvious separation makes it a little bit difficult to immediately visually distinguish between these two categories.
3 – Extremely tedious folder management: Just like in the previous version, inserting/removing pages and REs in folders is a nightmare. As already mentioned, it would be much more productive if it were possible to drag pages/REs or even have a multi-select ability to move these elements to folders.
4 – “Cut” names/labels: Now REs that have longer names are visually “cut” and you need to hover over them to see the full name (remember that the native Bubble tooltip used here when hovering has a delay, which does not improve the situation).
I know they added the ellipsis and nowrap properties here, but this whole problem could be fixed if we could have the ability to define a minimum/maximum size for this element window in a way that is best for each one, just like we have some canvas configuration options in “Grids & Guides” section, why not have some inputs in the “View” section that would allow this? Maybe even include a custom width for the elements tree and even other sections.
This is currently controlled by the classapp-interface-manager-side-panel with a current width fixed at 508px (I don’t know why this value is set). I believe that if each user could control this, adjusting the value to their work environment, monitor, etc., it would be the best option. Who knows, maybe even having the elements arranged in more columns if they wanted, for wider monitors.
I know, maybe someone will include this possibility in some browser extension, great. However, considering that many here, including myself, are not big fans of third-party extensions, it would be much better for Bubble to have this by default.
In addition to the above suggestion, with the change in width, another thing that would help fix these “cut” names would be to change the class app-interface-list-item width to 100% instead of being fixed at 234px.
5 – Loading thumbnails in REs returns to the top of the list: If we have the Element thumbnails option enabled, every time we hover over a RE, a load is performed and we are taken to the top of the list again. This may not be perceptible in apps with few REs, but in more complex and modular apps with a large number of REs this happens all the time, it is practically impossible to select an RE from the list without having to search for it.
4 Likes
First impressions of the new page manager layout is that it’s good and will be helpful. Have already started organising into folders including one for reusables. My wishes:
-
Display pages in a single list. Consistent with the workflow editor folders. Less clutter for brain. [ie, just one vertical column, not spread horizontally]
-
Allow folder renaming. (including that default “Web” one which should be “Uncategorized” imo)
-
Hide the pages from the “Web” folder when moved to a new folder.
All these simply make it consistent with the behavour of the workflows editor.
EDIT - After using it for 30 mins i can confirm it is SO slow and crashes the browser. I have 32 gig memory. unbelievable really such a simple & basic thing such this can break powerful machine in 2025. Bubble I love you so much but you really need to get your act together.
EDIT 2 - After NEATLY organising all my pages, I reload the browser only to find that bubble defaults them all to OPEN folders, creating an ugly sprawling mess. 
Jeeze. Please allow it to close the folders by default or remember previous state.
I think a benefit here is that you can group those pages into an admin folder or test folder
It would be a benefit if you didn’t have to go one by one to organize your whole app.
Good theory - bad practice by Bubble on this one
Yeah, except as others have pointed out:
-It’s kind of like messing up someone’s file system and then saying it’s ok because you give them a bunch of folders. That’s still making the UX worse and putting the onus on the user to fix the problem you created
-The process to actually move a page to a folder is tedious and laggy
Plus, having folders is useless if moving a page into a folder doesn’t actually work properly. When I tried moving a page to a folder, it didn’t even move it. I tried refreshing the page and it ended up putting it in two locations (“Web” and the folder), but the one on web just had a spinning icon. Eventually, it “worked” (after a full browser restart), but now the page is just in both places, which is not helpful at all.
Look, I understand the team is trying to improve the editor, and I’ve been trying to give them grace as they do it. But this, along with many other changes, it quite simply a downgrade in both performance and UX, not to mention it clearly wasn’t well-tested.
1 Like
Firefox developer edition is what I moved to. Used to have issues with chrome on my larger apps but haven’t since the switch.
It has no hard memory limit per tab, 64x systems it can use virtually all available ram, it handles unloading really well, and has a ton of built in tools for developers.
10 Likes
I wish the people who work at Bubble who were hired as Bubble devs would bring these points to those in their office negatively impacting their workflows.
To me, this is simply a failure of the product manager to learn from all the past mistakes by Bubble over the past 36 months…so easy to figure out how to properly launch a new feature, especially since the step by step guide has been written for them numerous times.
14 Likes
I have said this before but it should be a requirement (or financially incentivized) for all product/engineering employees to build their own Bubble app.
1 Like
Really hoping this can be fixed sooner rather than later. It feels like we’ve gone back to the editor performance early last year where it will crash multiple times a day.
It already is isn’t it @fede.bubble?