Editor crashes, ignored bug reports, and a month of silence. Is it really acceptable?

I need to share something that’s been seriously impacting my work, because I’m at a point where I genuinely don’t know what to expect from this platform anymore.

About a month ago I identified and reported an editor bug: when a Repeating Group’s cell’s container layout is set to Fixed, the editor starts lagging severely and eventually crashes. Fans going crazy, the browser throwing a “page unresponsive” warning, have to force close the browser .. that sort of crash. Switching the layout away from Fixed restores performance instantly. It’s consistent and reproducible.

I submitted multiple support tickets, I sent screen recordings, I did all the troubleshooting. I even found the root cause myself. The ticket finally reached the engineering team.

That was a month ago. Nothing has been fixed.

Since the RG layout bug was never fixed, eventually I had to use a bunch of CSS to mimic the cell’s fixed layout behaviour. I’m building a floor plan, fixed layout is not a nice thing to have, it’s absolutely necessary.

After pushing for an update, this is what I got from the specialised support team:
“Our engineering team’s investigation is still ongoing, and they’ve been discussing priority over a fix. They’ve taken an initial look and deployed some optimisations, only for the behaviour to persist.”
Their suggested workaround: reduce the number of groups inside the RG to a fixed size. (Ha? .. meaning “what?”)
And “discussing priority” after a month, on a reproducible crash that affects core editor functionality?

In the meantime, I’ve been dealing with separate, unrelated editor crashes on two major builds I’ve been working on for weeks. The editor is now working, 10 minutes later it doesn’t, it’s throwing a page unresponsive warning, fans go into overdrive and eventually crashes. Not as bad as the crash caused by the fixed RG layout bug but serious enough to make me abandon the work. There is no clear cause, no pattern I can pin down. It could be a group, a RG, a plugin … something specific is causing it but there’s no way to isolate it. Just an editor that becomes genuinely unreliable for serious work. And then, just to make it more baffling, in some cases, I come back to the same Reusable a week later and it works perfectly fine.

When I reported this, the response was:
“We’re looking to understand why this is occurring as soon as our team can.”
As soon as they can. I’m fully reliant on this platform for that built. What am I supposed to do in the meantime?

Bubble is actively working on a new editor UI redesign right now that nobody asked for. But when a bug that crashes the editor is sitting with engineering for a month with no fix and no timeline, it’s hard to understand where the priorities actually are.
Bugs happen, that’s fine. But a month of silence on something this serious, followed by “we’re discussing priority”? That’s a trust problem.

Is anyone else experiencing consistent editor crashes (this is unrelated to the usual editor heaviness)?
How does Bubble see this, when the core of what they are, the editor itself, is unreliable for serious builds?

I’ve been building on Bubble for over 3 years but right now I can’t trust the platform with serious, time-sensitive work. And I’d genuinely like to know if others feel the same.

2 Likes

I haven’t experienced this specific issue myself; the team has always addressed problems in a timely manner. However, I’m starting to notice a change in the forum and the community support side. It feels like something is happening within the Bubble ecosystem that suggests a step back or a stagnation in development. This is strange, considering the updates shared by the team regarding shipped features or ongoing development. I don’t really know what to think about it at the moment.

hey @dianabologabv, I’m going to ask around internally, see if I can find some more info

Thanks for following up. I appreciate you asking around. I did receive an update last night from the specialised team: “We haven’t received new updates from the team just yet. We appreciate your continued patience.” After 1 month, there’s no timeline, no fix, no clear path forward.

In the meantime I now have two builds completely unusable due to editor crashes.
This one below is the actual floor plan I’ve been working on for over a week. The Floor plan with all the CSS workaround that deals with the RG bug.
It’s almost complete, was doing final tweaks and testing, was working fine up until yesterday - until it wasn’t. I click around a couple of times, the editor becomes slow and lagging and the browser crashes.

The thing is, this isn’t the first time this happened. Last year I had the same issues, it took engineers over a month to fix. I didn’t wait then … i rebuilt everything from scratch and used loads of nested reusables to keep the editor stable (almost every section/RG/parent group container inside a Reusable was a Reusable). Needless to say, it was a nightmare. When the bugs was fixed and the editor got stable again I rebuilt again properly. So I basically built the same thing 3 times.

So I’m asking, what am I supposed to do here? wait indefinitely while two major features sit unusable? rebuild again and hope it doesn’t crash this time? Or accept that Bubble is unreliable for serious production work and move on to a different platform.
These are rhetorical questions, obviously… but the fact that I’m even asking them says everything about where things stand. It clearly highlights the reality and the gravity of the situation.

Hello, welcome to the dark side, you need to use issue_checkeroff. Add this &issues_off=true to the end of url of the editor.

I think if wf number is >250 you need issues off

1 Like


Turning this off also helps with editor crashes as well.

Only if it were that easy; it’s not the heaviness, the editor crashes for no obvious reason. This particular RE is light weight, a couple of RGs with shapes and images in it, the JS does most of the heavy lifting. And very few WFs.

A couple of weeks ago I added a multi dropdown inside a RG and my laptop started screaming for help … removing it calmed the waters instantly. So there’s something very specific, certain layout related things maybe that triggers the crawlers and the editor is full of them. Same with the RG cell’s fixed container layout bug .. luckily I could trace back my steps and found the root cause.

thanks! it’s always off, unless I’m creating backend workflows

1 Like

Interesting

This has been my life for a very long time – both on powerful PCs and Macs. I’m just used to it (which is sad). I even have a mouse button programmed for a browser refresh, just in honor of Bubble. And switching branches or merges are the same story.

Passionate advice. Insert in your editor url &issues_off=true. It will work again.

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