Skip to content

Lots of errors from flutter run + android emulator #9864

Closed

Description

@sethladd

Not sure if this is normal, but using flutter run and an android emulator, I see a never-ending repeat of the following, anytime something interacts with the emulator screen:

E/libGLESv2_swiftshader( 3117): badness: unimplemented: IsColorRenderable vendor/transgaming/swiftshader_source/src/OpenGL/libGLESv2/utilities.cpp:1059
E/swiftshader( 3117): AndroidEnterDebugger
E/libGLESv2_swiftshader( 3117): badness: unimplemented: IsColorRenderable vendor/transgaming/swiftshader_source/src/OpenGL/libGLESv2/utilities.cpp:1059

and, after I type 'r' in the console, I see:

Initializing hot reload...
E/libGLESv2_swiftshader( 3117): badness: unimplemented: IsColorRenderable vendor/transgaming/swiftshader_source/src/OpenGL/libGLESv2/utilities.cpp:1059
E/swiftshader( 3117): AndroidEnterDebugger
E/libGLESv2_swiftshader( 3117): badness: unimplemented: IsColorRenderable vendor/transgaming/swiftshader_source/src/OpenGL/libGLESv2/utilities.cpp:1059
E/swiftshader( 3117): AndroidEnterDebugger
E/libGLESv2_swiftshader( 3117): badness: unimplemented: IsColorRenderable vendor/transgaming/swiftshader_source/src/OpenGL/libGLESv2/utilities.cpp:1059
E/swiftshader( 3117): AndroidEnterDebugger
Reloaded 412 of 427 libraries in 1,177ms.
E/libGLESv2_swiftshader( 3117): badness: unimplemented: IsColorRenderable vendor/transgaming/swiftshader_source/src/OpenGL/libGLESv2/utilities.cpp:1059
E/swiftshader( 3117): AndroidEnterDebugger
E/libGLESv2_swiftshader( 3117): badness: unimplemented: IsColorRenderable vendor/transgaming/swiftshader_source/src/OpenGL/libGLESv2/utilities.cpp:1059
E/swiftshader( 3117): AndroidEnterDebugger
E/libGLESv2_swiftshader( 3117): badness: unimplemented: IsColorRenderable vendor/transgaming/swiftshader_source/src/OpenGL/libGLESv2/utilities.cpp:1059
E/swiftshader( 3117): AndroidEnterDebugger

Is this normal, or is this from the combo of android emulator and Flutter?

Impact on the developer: if anything else is ever printed to the console, it will be lost :) Also, it's not clear I can type 'r' because there's no "prompt" and it looks like a stream of log/error messages.

FWIW, this may or may not be useful. This is the output from running the emulator:

C:\Users\sethladd\AppData\Local\Android\Sdk\tools>emulator -skin 1080x1920 -avd Foo1
emulator: WARNING: encryption is off
Hax is enabled
Hax ram_size 0x40000000
HAX is working and emulator runs in fast virt mode.

Activity

  1. eseidelGoogle commented on May 8, 2017

    @eseidelGoogle
    Contributor
  2. chinmaygarde commented on May 8, 2017

    @chinmaygarde
    Contributor

    That emulator seems to be implementing OpenGL ES support using SwiftShader which is complaining about unimplemented features. The logs don't originate from the engine.

  3. sethladd commented on May 8, 2017

    @sethladd
    ContributorAuthor

    Are these errors benign ? Should we hide them?

    Or, did I do something wrong when I setup my AVD?

  4. chinmaygarde commented on May 8, 2017

    @chinmaygarde
    Contributor

    Yes, those errors should be benign. Its just that some other library is logging to logcat.

  5. Hixie commented on May 8, 2017

    @Hixie
    Contributor

    Is 3117 our pid, in these logs?

  6. added this to the milestone on Jan 3, 2018
  7. zoechi commented on Dec 18, 2018

    @zoechi
    Contributor

    Is this issue still relevant?

  8. vanhoutenbos commented on Dec 21, 2018

    @vanhoutenbos

    I have encountered this issue today.
    Steps to reproduce:
    Start Visual Studio 2017
    Create a Xamarin Forms project
    Start emulator.

  9. Hixie commented on Jan 16, 2019

    @Hixie
    Contributor

    We're just going to close this because it's not clear what exactly the issue here is.

    @jeanpoelie If you do see this, please file a new bug with exact steps to reproduce -- when you file the bug, it'll prompt you for information we need (like your flutter version). Thanks!

  10. added a commit that references this issue on Sep 11, 2019
  11. added a commit that references this issue on Sep 12, 2019
  12. added a commit that references this issue on Sep 12, 2019
  13. added a commit that references this issue on Sep 13, 2019
  14. added a commit that references this issue on Sep 13, 2019
  15. github-actions commented on Aug 15, 2021

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  16. locked as resolved and limited conversation to collaborators on Aug 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    e: device-specificOnly manifests on certain devicesplatform-androidAndroid applications specificallywill need additional triageThis issue or PR needs attention before being routed to secondary triage

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions