Flutter-intellij: Running flutter app in emulator freezes windows

Created on 21 Apr 2020  Â·  11Comments  Â·  Source: flutter/flutter-intellij

Steps to Reproduce

  1. Create a sample flutter project in the IDE.
  2. Create a virtual device in AVD Manager
    image
    image
    image

  3. Run the app on the emulator. Windows Just freezes. Only option left to restart the system using the power button.

  4. Just starting the emulator in the AVD Manager takes up lot of time. Below issues are recorded in the event log with running the app.
    `7:30 PM Emulator: glTexImage2D: got err pre :( 0x502 internal 0x1908 format 0x1908 type 0x1401

7:30 PM Emulator: glTexImage2D: got err :( 0x502 internal 0x1908 format 0x1908 type 0x1401

7:30 PM Emulator: glTexImage2D: got err pre :( 0x502 internal 0x1908 format 0x1908 type 0x1401

7:30 PM Emulator: glTexImage2D: got err :( 0x502 internal 0x1908 format 0x1908 type 0x1401

7:30 PM Emulator: C:buildbotsrcandroidemu-master-devexternalqemuandroidandroid-emuglhostlibsTranslatorGLES_V2GLESv2Imp.cpp:glPixelStorei:3024 error 0x501

7:30 PM Emulator: glTexImage2D: got err pre :( 0x502 internal 0x1908 format 0x1908 type 0x1401

7:30 PM Emulator: C:buildbotsrcandroide

7:30 PM Emulator: mu-master-devexternalqemuandroidandroid-emuglhostlibsTranslatorGLES_V2GLESv2I

7:30 PM Emulator: mp.cpp:glGetAttachedShaders:1763 error 0x501

7:30 PM Emulator: C:buildbotsrcandroidemu-master-devexter

7:30 PM Emulator: nalqemuandroidandroid-emuglhostlibsTranslatorGLES_V2GLESv2Imp.cpp:glGetAttachedShaders:1763 error 0x501

7:30 PM Emulator: C:buildbotsrcandroidemu-master-devexternalqemuandroidandroid-emuglhostlibsTranslatorGLES_V2GLESv2Imp.cpp:glDeleteProgram:1220 error 0x501

7:30 PM Emulator: C:buildbotsrcandroidemu-master-devexternalqemu

7:30 PM Emulator: androidandroid-emuglhostlibsTranslatorGLES_V2GLESv2Imp.cpp:glDeleteProgram:1220 error 0x501

7:46 PM Emulator: Process finished with exit code 0

7:48 PM Emulator: emulator: ERROR: VkCommonOperations.cpp:496: Failed to create Vulkan instance.

7:51 PM Emulator: emulator: INFO: QtLogger.cpp:68: Critical: Uncaught TypeError: Cannot read property 'update' of undefined (qrc:/html/js/common.js:130, (null))

7:53 PM Emulator: emulator: ERROR: AdbHostServer.cpp:83: adb protocol fault (couldn't read status len

7:53 PM Emulator: gth)

8:27 PM Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU0 thread'. No response for 15153 ms

8:30 PM Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU0 thread'. No response for 15001 ms

10:37 PM Emulator: Process finished with exit code 255`

  1. Trying to run the app just freezes whole windows and need to power cycle
  2. SDK versions
    image

Version info

[√] Flutter (Channel master, v1.18.0-6.0.pre.82, on Microsoft Windows [Version 10.0.17763.1098], locale en-US)
• Flutter version 1.18.0-6.0.pre.82 at C:srcflutter
• Framework revision f35b673f2b (3 days ago), 2020-04-19 02:45:01 +0530
• Engine revision a5e0b2f2f2
• Dart version 2.9.0 (build 2.9.0-1.0.dev 5b19445d9c)

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
• Android SDK at C:Androidsdk
• Platform android-29, build-tools 29.0.3
• ANDROID_SDK_ROOT = C:Androidsdk
• Java binary at: C:Program FilesAndroidAndroid Studiojrebinjava
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
• All Android licenses accepted.

[√] Visual Studio - develop for Windows (Visual Studio Professional 2019 16.4.5)
• Visual Studio at C:Program Files (x86)Microsoft Visual Studio2019Professional
• Visual Studio Professional 2019 version 16.4.29806.167

[√] Android Studio (version 3.6)
• Android Studio at C:Program FilesAndroidAndroid Studio
• Flutter plugin version 45.1.1
• Dart plugin version 192.7761
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)

[√] VS Code (version 1.44.1)
• VS Code at C:Users527980AppDataLocalProgramsMicrosoft VS Code
• Flutter extension version 3.9.1

[√] Connected device (2 available)
• Android SDK built for x86 • emulator-5554 • android-x86 • Android 10 (API 29) (emulator)
• Windows • Windows • windows-x64 • Microsoft Windows [Version 10.0.17763.1098]

• No issues found!

waiting for customer response

Most helpful comment

Having the same issue. Where do I find the log files?

Got it sorted out. I deleted the /.dart_tool, /.idea and /build (everything inside) folders from my project directory and everything started working again.

All 11 comments

I am also having the same problem.

Having the same issue. Where do I find the log files?

Having the same issue. Where do I find the log files?

Got it sorted out. I deleted the /.dart_tool, /.idea and /build (everything inside) folders from my project directory and everything started working again.

I observed it to happen when gradle updates to a new version. Deleting the project build folder solves the issue.

Having similar kind of problem
I dont know why its happening but i guess after an update it is causing

@stevemessick: do you know if this is an ongoing issue?

@pq I don't know. It sounds like a problem with Flutter upgrading and not clearing its cache. Doesn't sound like an IDE issue.

Got it. Thanks.

@sohelakhtar23, @adityasreebysani, @firestormza: are any of you still seeing this?

I've only had the problem once.

No I haven't faced the problem in recent times. However, lately I have
started using VS Code and I am no longer using Android Studio due to
general performance issues.

So not sure if the problem was in IDE or Flutter.

On Tue, Aug 4, 2020, 4:35 AM firestormza notifications@github.com wrote:

I've only had the problem once.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter-intellij/issues/4497#issuecomment-668282654,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB5A2FYQHXE2LVBHIW6H7X3R647DNANCNFSM4MNHJLHA
.

Without additional information we're unfortunately not sure how to resolve this issue. We're going to close this bug for now, but please don't hesitate to comment on the bug if you have any more information for us; we're happy to reopen. Thanks for your contribution!

Was this page helpful?
0 / 5 - 0 ratings