I"m getting this on the console while running the initial counter app that comes default with flutter. How do i fix this?

Question

This is most of what i get in the debug console when i run the initial flutter app that comes with flutter. This does not look normal. What should i do to fix this?

 Built build/app/outputs/apk/debug/app-debug.apk.
D/FlutterActivity(12595): Using the launch theme as normal theme.
D/FlutterActivityAndFragmentDelegate(12595): Setting up FlutterEngine.
D/FlutterActivityAndFragmentDelegate(12595): No preferred FlutterEngine was provided. Creating a new FlutterEngine for this FlutterFragment.
D/FlutterActivityAndFragmentDelegate(12595): Attaching FlutterEngine to the Activity that owns this Fragment.
D/FlutterView(12595): Attaching to a FlutterEngine: io.flutter.embedding.engine.FlutterEngine@ad2d938
D/FlutterActivityAndFragmentDelegate(12595): Executing Dart entrypoint: main, and sending initial route: /
D/HostConnection(12595): HostComposition ext ANDROID_EMU_CHECKSUM_HELPER_v1 ANDROID_EMU_native_sync_v2 ANDROID_EMU_native_sync_v3 ANDROID_EMU_native_sync_v4 ANDROID_EMU_dma_v1 ANDROID_EMU_direct_mem ANDROID_EMU_host_composition_v1 ANDROID_EMU_host_composition_v2 ANDROID_EMU_YUV420_888_to_NV21 ANDROID_EMU_YUV_Cache ANDROID_EMU_async_unmap_buffer GL_OES_EGL_image_external_essl3 GL_OES_vertex_array_object GL_KHR_texture_compression_astc_ldr ANDROID_EMU_gles_max_version_3_0
I/Choreographer(12595): Skipped 913 frames!  The application may be doing too much work on its main thread.
D/EGL_emulation(12595): eglMakeCurrent: 0xe02eec60: ver 3 0 (tinfo 0xe030ba70)
D/EGL_emulation(12595): eglMakeCurrent: 0xeb57f3a0: ver 3 0 (tinfo 0xe038db30)
D/EGL_emulation(12595): eglMakeCurrent: 0xe02eede0: ver 3 0 (tinfo 0xe030ba70)
D/EGL_emulation(12595): eglMakeCurrent: 0xeb57f3a0: ver 3 0 (tinfo 0xe038db30)
D/FlutterView(12595): Detaching from a FlutterEngine: io.flutter.embedding.engine.FlutterEngine@ad2d938
D/FlutterView(12595): Detaching from a FlutterEngine: io.flutter.embedding.engine.FlutterEngine@ad2d938
D/EGL_emulation(12595): eglMakeCurrent: 0xeb57f3a0: ver 3 0 (tinfo 0xe038db30)
D/FlutterView(12595): Attaching to a FlutterEngine: io.flutter.embedding.engine.FlutterEngine@ad2d938
D/EGL_emulation(12595): eglCreateContext: 0xe02eede0: maj 3 min 0 rcv 3
D/EGL_emulation(12595): eglMakeCurrent: 0xe02eede0: ver 3 0 (tinfo 0xe030ba70)
I/Choreographer(12595): Skipped 176 frames!  The application may be doing too much work on its main thread.
D/EGL_emulation(12595): eglMakeCurrent: 0xeb57f3a0: ver 3 0 (tinfo 0xe038db30)
D/FlutterView(12595): Attaching to a FlutterEngine: io.flutter.embedding.engine.FlutterEngine@ad2d938
D/EGL_emulation(12595): eglCreateContext: 0xd4b696e0: maj 3 min 0 rcv 3
D/EGL_emulation(12595): eglMakeCurrent: 0xd4b696e0: ver 3 0 (tinfo 0xe030ba70)
I/Choreographer(12595): Skipped 66 frames!  The application may be doing too much work on its main thread.
D/EGL_emulation(12595): eglMakeCurrent: 0xd4b696e0: ver 3 0 (tinfo 0xe030ba70)
Reloaded 1 of 478 libraries in 2,280ms.

Answer 1

I faced the same issue once. The problem solved when I ran the application by pointing to the release mode. Please try flutter run --release instead of flutter run

Answer 2

Assuming you haven't touched the starter code, the fact that the skipped frames declines as you run it tells me that this is a natural byproduct of running an emulator on your machine. Generally, < 100 skipped frames in these messages can be safely ignored--it means your computer is having a hard time running the emulator in real-time.

Put your physical Android device into debugging mode and then use a cable to connect it, then select that device as your build target. If you run the app on your phone, do you still get skipped frames? If you are running any sort of modern Android phone, you generally will not.

The Android emulators take a lot of processing power to run. Most people generally agree that debugging on a physical device is several times faster than debugging through an emulator.