Flutter Question posted in
The official Flutter documentation can be found here.

Excessive Logging After Flutter SDK Update: exportSyncFdForQSRILocked and sendCancelIfRunning Messages

I recently updated my Flutter SDK to the latest version (3.27.0) and am encountering excessive logging in the console whenever I run my Flutter project on an Android device. The logs include repeated messages like these:

W/WindowOnBackDispatcher( 5712): sendCancelIfRunning: isInProgress=false callback=io.flutter.embedding.android.FlutterActivity$1@775be57
I/MESA    ( 5712): exportSyncFdForQSRILocked: call for image 0xb400007aaf063850 hos timage handle 0x70002000000d3
I/MESA    ( 5712): exportSyncFdForQSRILocked: got fd: 168
I/MESA    ( 5712): exportSyncFdForQSRILocked: call for image 0xb400007aaf07dd50 hos timage handle 0x70002000000d4
I/MESA    ( 5712): exportSyncFdForQSRILocked: got fd: 170

[GETX] GOING TO ROUTE /login
[GETX] Instance "LoginController" has been created
[GETX] Instance "LoginController" has been initialized
I/MESA    ( 5712): exportSyncFdForQSRILocked: call for image 0xb400007aaf0633d0 hos timage handle 0x70002000000d1
I/MESA    ( 5712): exportSyncFdForQSRILocked: got fd: 166

These logs seem to originate from Flutter or the Android system and are not helpful for debugging my application. It clutters the console and makes it hard to focus on relevant logs.

What I’ve Tried

  1. Rebuilding the project (flutter clean and flutter pub get).
  2. Checking for issues in my project code (nothing obvious so far).
  3. Ensuring that all plugins and dependencies are updated to the latest versions.
Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    Temporary Solution (Only for Android Studio Users)

    1. Open Run/Debug Configurations
      Navigate to Run → Edit Configurations in Android Studio.


      Open Configurations

    2. Add the Flag
      In the Additional run args section, paste the following:

      --no-enable-impeller

      Click Apply and then OK to save the changes.


      Add Flag and Apply


  2. 0

    There is ticket for this here: https://github.com/flutter/flutter/issues/160442

    But in the meanwhile a temporary solution would be to add --no-enable-impeller to your run command.

    Ex: flutter run --no-enable-impeller

    Hope that helps.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search