Now, the same thing happened when I edited the HTML in WebView and reloaded the Chrome local run I had running.

Thank you for your report! I followed the steps you mentioned but was unable to replicate the issue. To assist you better, could you please share the full crash logs in a .txt file instead of the screenshot? Having the complete trace will allow our team to troubleshoot the problem more effectively.

Looking forward to your response, and we appreciate your patience!

The problem is that when I force closing the FF App I'm not getting any crash report.

➕1️⃣
Happens at random times. I haven't been able to figure it out.

I have the same issue too, it appears randomly when trying to reload a local run

same issue here, on my mac

It does happen at random times but I also have seen it happen a good amount of time when I click open the Test (down arrow), and while the Run mode links are still loading, and I click on get devices or hot reload, it is pretty much gauranteed to freeze, so now I exercise a meditation mode each time I click on that down arrow button.

Hello!!

Thanks so much for all your reports — I’ll pass this issue along to the engineering team so they can take a closer look.

Hi,
i also noticed a real increase heat on my laptop ( runing on a Apple M1 Max 2021, 32GB, Total Number of Cores: 10 (8 performance and 2 efficiency)
so after around 2 hours of FF work, the laptop heats up and the app is slow.
That doesnt happen while FF desktop app is closed and even having Photoshop, Docker and few others app running simultaniously )
That doesnt happen on FF web

FF v 5.2.8 issue persists.

+1 Was about to email support - App keeps getting into a non-responsive state. @Alezanello Here is more data for your team to work with.
Mac Book Pro - Apple Chip 2023. Running Flutterflow Desktop and this shows each time I open it "FlutterFlow 5.2.8 is currently the newest version available"

I concur with @nvimalraj about the link to the Test button/Test functionality usage - from a clean start I am good building in the designer. My issues start and keep happening after I have used the local run capabilities. I have a WebApp and use the [Get Devices > Local Run > Chrome] to test against.

Note: I do not have Firebase or Crashlytics enabled/setup in my project settings.

Apple must be getting sick of receiving my crash reports. I ran one through ChatGPT and here is the diagnosis from it.

ChatGPT:
The stack log shows that the app’s main thread is being blocked by a call chain coming from the Firebase Crashlytics plugin. In particular, the log points to methods such as:

•   -[FLTFirebaseCrashlyticsPlugin handleMethodCall:result:]
•   -[FLTFirebaseCrashlyticsPlugin recordError:withMethodCallResult:]
•   then into Crashlytics’ on‑demand exception recording (e.g. FIRCLSOnDemandModel methods)

This chain eventually leads to a synchronous file system call (via NSFileManager’s attributesOfItem:atPath:) and subsequent memory allocation functions. These operations appear to be waiting (as indicated by repeated “psynch_cvcontinue” calls and being blocked by a kernel turnstile) and, because they’re executing on the main thread, they prevent the app’s UI from responding.

In short, the app becomes unresponsive because the Crashlytics plugin is executing a synchronous (blocking) file I/O operation on the main thread while recording an error/exception. This causes the main thread to hang, which in turn makes the app appear “not responding.”

To address this, you might consider: • Offloading such file I/O or error recording work to a background thread. • Checking if there is an update or patch for the Firebase Crashlytics plugin that fixes this synchronous behavior. • Reviewing how and when errors are reported to Crashlytics in your FlutterFlow app.

By ensuring that heavy operations (especially file system interactions) are not done on the main thread, you can prevent the UI from freezing.

I just got an error when reloading the local run. With the new FlutterFlow version, I got an option to send the report to the developer, which I did.

This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.

Not a lot of help but I saw this too however I have also seen freezes in Chrome on Mac and the web based version too. So it may not be limited to the desktop app (in fact isn't the desktop app basically Chrome?). So it might be more to do with Chrome.

The freezes are random, can't do steps to repo.

Same problem here. What I've noticed is that I need to wait around 10 seconds after making any change before I can refresh the test on my devices without it freezing.

To be honest, it's a bit annoying, but at least I've managed to reduce the freezing issue (yeah, I said reduce, not eliminate it).

FF v5.3.7 issue is still occurring, especially when refreshing the local run.

This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.

Still waiting and still occurs on 5.3.7

This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.

The issue is still present in the latest version of FlutterFlow.

This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.

Issue still present in the FF 5.4.5.

cross reference #5594

For someone who spends hours on a daily basis in FlutterFlow, this is a very frustrating issue.

@Alezanello do you have any timeline for the fix?