Flutter 3.29.0 Update Causes "E/libEGL: called unimplemented OpenGL ES API" on BlueStacks.

[yesilcimenahmet]

Description:

After updating Flutter to version 3.29.0, I started encountering the following error repeatedly in the console when running my app on BlueStacks:

E/libEGL ( 4823): called unimplemented OpenGL ES API

ABI: x86 64-bit

BlueStacks 5.21.661.1002 P64

flutter doctor -v

[√] Flutter (Channel stable, 3.29.0, on Microsoft Windows [Version 10.0.26100.3194], locale tr-TR) [413ms]
    • Flutter version 3.29.0 on channel stable at D:\fluttersdk\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 35c388afb5 (3 days ago), 2025-02-10 12:48:41 -0800
    • Engine revision f73bfc4522
    • Dart version 3.7.0
    • DevTools version 2.42.2

[√] Windows Version (11 Pro 64-bit, 24H2, 2009) [2,4s]

[√] Android toolchain - develop for Android devices (Android SDK version 35.0.0) [2,0s]
    • Android SDK at C:\Users\user\AppData\Local\Android\sdk
    • Platform android-35, build-tools 35.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jbr\bin\java
      This is the JDK bundled with the latest Android Studio installation on this machine.
      To manually set the JDK path, use: `flutter config --jdk-dir="path/to/jdk"`.
    • Java version OpenJDK Runtime Environment (build 21.0.5+-12932927-b750.29)
    • All Android licenses accepted.

[√] Chrome - develop for the web [106ms]
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.13.0) [105ms]
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.13.35806.99
    • Windows 10 SDK version 10.0.22621.0

[√] Android Studio (version 2024.2) [28ms]
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 21.0.5+-12932927-b750.29)

[√] VS Code (version 1.97.2) [26ms]
    • VS Code at C:\Users\user\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension can be installed from:
       https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[√] Connected device (4 available) [251ms]
    • SM G998B (mobile) • emulator-5554 • android-x64    • Android 9 (API 28)
    • Windows (desktop) • windows       • windows-x64    • Microsoft Windows [Version 10.0.26100.3194]
    • Chrome (web)      • chrome        • web-javascript • Google Chrome 133.0.6943.99
    • Edge (web)        • edge          • web-javascript • Microsoft Edge 133.0.3065.59

[√] Network resources [437ms]
    • All expected network resources are available.

• No issues found!

[HaydenOH]

same issue 😭

[yesilcimenahmet]

@HaydenOH have you experienced any side effects?

[HaydenOH]

It doesn't happen very often, but sometimes it dies right after the app is built. But I don't know if it's caused by this problem. When the app is working, it only logs and seems to have no effect

[jonahwilliams]

Unless there is a stack trace or some other obvious negative effect (like a crash), I'm inclined to believe this is just unfortuante logspam from android. We could hide the error message in the flutter tool (if this is via flutter run), otherwise 🤷

[jason-simmons]

I'm also seeing this message when running on a standard Android SDK emulator.

It's coming from the glDebugMessageControlKHR call made by the ReactorGLES. Somehow that API is resolving to a non-null function pointer even though it's apparently not actually supported by the emulator.

The GLES backend may need to gate that call on the presence of the KHR_debug extension.

[jonahwilliams]

Ahh that makes sense. Checking for function ptrs is not really safe, we shoud fix that.

Good news is that should only be used in debug mode/profile mode for tracing IIRC.

[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.