Skip to content

Black screen when running flutter in mojo after engine update #4957

Closed

Description

@mikejurka

Steps to Reproduce

Running a flutter app through mojo. After applying (aff8e30) I get a black screen.

Flutter Doctor

Paste the output of running flutter doctor here.

Black screen flutter:
[✓] Flutter (on Mac OS, channel unknown)
• Flutter at /Users/mikejurka/code/sysui/src/third_party/flutter
• Framework revision 94d1104 (3 days ago), engine revision 2d65102

[✓] Android toolchain - develop for Android devices (Android SDK 23.0.3)
• Android SDK at /Users/mikejurka/Library/Android/sdk
• Platform android-23, build-tools 23.0.3
• Java(TM) SE Runtime Environment (build 1.8.0_91-b14)

[✓] iOS toolchain - develop for iOS devices (Xcode 7.3.1)
• XCode at /Applications/Xcode.app/Contents/Developer
• Xcode 7.3.1, Build version 7D1014

[✓] Atom - a lightweight development environment for Flutter
• flutter plugin version 0.2.3
• dartlang plugin version 0.6.29

Version that works ok:
[✓] Flutter (on Mac OS, channel unknown)
• Flutter at /Users/mikejurka/code/sysui/src/third_party/flutter
• Framework revision d33da2f (5 days ago), engine revision a218688

[✓] Android toolchain - develop for Android devices (Android SDK 23.0.3)
• Android SDK at /Users/mikejurka/Library/Android/sdk
• Platform android-23, build-tools 23.0.3
• Java(TM) SE Runtime Environment (build 1.8.0_91-b14)

[✓] iOS toolchain - develop for iOS devices (Xcode 7.3.1)
• XCode at /Applications/Xcode.app/Contents/Developer
• Xcode 7.3.1, Build version 7D1014

[✓] Atom - a lightweight development environment for Flutter
• flutter plugin version 0.2.3
• dartlang plugin version 0.6.29

Logs and Crash Reports

No logs that point to any issues

For more information about diagnosing and reporting Flutter bugs, please see https://flutter.io/bug-reports/.

Activity

  1. added this to the milestone on Jul 18, 2016
  2. abarth commented on Jul 18, 2016

    @abarth
    Contributor
  3. self-assigned this
    on Jul 19, 2016
  4. mikejurka commented on Jul 19, 2016

    @mikejurka
    ContributorAuthor

    Tried the latest version of the engine, still seeing a black screen:
    [✓] Flutter (on Mac OS, channel unknown)
    • Flutter at /Users/mikejurka/code/sysui/src/third_party/flutter
    • Framework revision ebc7e4b (18 hours ago), engine revision 3291ede

    [✓] Android toolchain - develop for Android devices (Android SDK 23.0.3)
    • Android SDK at /Users/mikejurka/Library/Android/sdk
    • Platform android-23, build-tools 23.0.3
    • Java(TM) SE Runtime Environment (build 1.8.0_91-b14)

    [✓] iOS toolchain - develop for iOS devices (Xcode 7.3.1)
    • XCode at /Applications/Xcode.app/Contents/Developer
    • Xcode 7.3.1, Build version 7D1014

    [✓] Atom - a lightweight development environment for Flutter
    • flutter plugin version 0.2.3
    • dartlang plugin version 0.6.29

    Reverting to the version of flutter using engine revision a218688 still works ok.

  5. pylaligand commented on Jul 26, 2016

    @pylaligand
    Contributor

    What's the status of this issue?

  6. modified the milestones: , August on Aug 1, 2016
  7. mikejurka commented on Aug 2, 2016

    @mikejurka
    ContributorAuthor

    I'm still seeing a black screen when running flutter on mojo.

    [✓] Flutter (on Mac OS, channel unknown)
    • Flutter at /Users/mikejurka/code/sysui/src/third_party/flutter
    • Framework revision 82b7fc0 (14 hours ago), engine revision 6320dd9

    [✓] Android toolchain - develop for Android devices (Android SDK 23.0.3)
    • Android SDK at /Users/mikejurka/Library/Android/sdk
    • Platform android-23, build-tools 23.0.3
    • Java(TM) SE Runtime Environment (build 1.8.0_91-b14)

    [✓] iOS toolchain - develop for iOS devices (Xcode 7.3.1)
    • XCode at /Applications/Xcode.app/Contents/Developer
    • Xcode 7.3.1, Build version 7D1014

    [✓] Atom - a lightweight development environment for Flutter
    • flutter plugin version 0.2.3
    • dartlang plugin version 0.6.29

  8. mikejurka commented on Aug 2, 2016

    @mikejurka
    ContributorAuthor

    I tested on both linux and android.

    On Android, you see a black screen.
    On Linux, you see the window frame but nothing painted inside of it.

    In the error logs, I'm seeing:
    "[0802/112125:WARNING:platform_view.cc(141)] WARNING: Could not setup an OpenGL context on the resource loader." I didn't see this when using an older working version of flutter; might be related but I'm not sure.

    Reverting flutter (Framework revision d33da2f (5 days ago), engine revision a218688) works normally

  9. chinmaygarde commented on Aug 2, 2016

    @chinmaygarde
    Contributor

    The warning is part of the patches that added asynchronous texture loading. Even in case of failure to setup the background texture loading context, texture loading should fallback to loading synchronously. I am testing again.

  10. mikejurka commented on Aug 2, 2016

    @mikejurka
    ContributorAuthor

    Ok, I think that warning is a red herring. We were getting the black screen even before seeing that message.

    This regression was introduced in:
    flutter-team-archive/engine@fe69b03

    Seems like lots of stuff about setting / changing context changed in that CL e.g. there were changes to sky/shell/platform/mojo/platform_view_mojo.cc and sky/shell/gpu/direct/ganesh_canvas.cc, among others. Not sure what exactly caused the issue, but it's pretty clear to me that the regression surfaced in that CL.

    I can definitely show repro steps if you don't have them.

  11. abarth commented on Aug 2, 2016

    @abarth
    Contributor

    Sounds like we messed up the Mozart configuration when we changed the GL startup sequence. @chinmaygarde Do you want to look at this regression or should I take a look?

  12. chinmaygarde commented on Aug 2, 2016

    @chinmaygarde
    Contributor

    @abarth Can you take a look please. I have verified that none of the rasterizer direct paths should affect the Mozart configurations.

  13. added a commit that references this issue on May 14, 2018
  14. github-actions commented on Sep 6, 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.

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions