Bubble has suddenly started crashing during a workflow run! This workflow has been stable for months, and I haven’t changed it.
This is URGENT - it is in a key part of my application and the remainder of the workflow doesn’t run. It happens during a simple database update.
Below are screenshots of the console when the app crashes. I have submitted bug report #6012.
However the problem is intermittent. I saw the same problem yesterday when a client was using my app and I thought they had an unstable internet connection. But now I know it was another occurrence of this bug.
Was thinking it was me, but I also see some sudden change in API workflow and also run in error that didn’t see before (operation timed out). Also, app take a lot of time to load.
Logged a bug report. Pages that shouldn’t be are throwing out-of-memory errors. Seen myself and been reported by users.
Also, as noted in bug report, while it may not be related to today’s problem, I remain EXTREMELY concerned about the massive numbers of “Uncaught Error: cast resulted in change” warnings that Bubble is throwing to the console. This simply can’t be helpful for performance.
Visit one of my widget pages, for example, and look at the console. It’s nothing but nonsense:
Well, I complained about those console logs the other day. But yeah, I actually think that they are killing my app. @Bubble, halp. See my bug report, but you really need to kill these “information warnings used by your developers”. They are running amok and killing my production app.
It’s weird – it seems likely it’s been affecting my app for a couple of days, but I hadn’t seen it cause my production app to cause web browsers to die from out-of-memory. But that indeed is what is happening now.
Seem that this may be hard to find the root issue but I think it’s related to specific unit/cluster. I duplicate one app that I have isisue and doesn’T have slow or timed out error (but keep the error in console but this is a different issue)
Well, I think they didn’t realize – as I didn’t – that it’s not just a minor nuisance, but that it is actually a thing that can bring down otherwise completely well-behaved apps. (My own is an example.)
I’m a lil’ pissed at myself for not checking this out sooner, but these notification haven’t just made my plugin development a pain, but they are actually causing my site (and my customers’ sites) to blow up user’s browsers.
@emmanuel I was literally about to press send on a very desperate message to you and Josh. My entire career right now depends on my trust with you guys, and these last couple of days have felt really tough for some of us.
They are seemingly not errors. I started seeing little bits of these several months ago and asked about it. Was told they are warnings coming from the product intended for dev.
They are fine in moderation. And, of course, I LOVE me some console.logs… and use them extensively. But I mostly remove them for production.
On a very happy note: The offending messages are gone and my app works normally once again.
