GPUAUX error spam with a WebGL application in inappwebview

[berkbuzcu]

• I have read the Getting Started section
• I have already searched for the same problem

Environment

Technology	Version
Flutter version	3.9.15
Plugin version	6.0.0
Android version	14.0
iOS version	-
macOS version	-
Xcode version	-
Google Chrome version	-

Device information: Xiaomi Pad Model 22081283G

Description

Expected behavior: Host a tiny webpage with three.js to show 3D FBX models using WebGL.

Current behavior: It works, but the console is full of errors in Xiaomi Pad Model 22081283G as seen in Stacktrace section.

It is specifically odd because the application appears to work as intended. The error is not repeated in other devices. I believe this might be an issue with WebGL -> GLES pass but I wanted to ask if anyone encountered this here first.

Steps to reproduce

1. Build any three.js HTML with a single model from maximo FBX format.
2. Host index.html with Three.JS code in localhost using the plugin.
3. Create a view that connects to the website and shows the model.

Stacktrace/Logcat

E/ble_prototype(24833): == MALI DEBUG ===BAD ALLOC from gles_texture_egl_image_get_2d_template err is 0
E/GPUAUX (24833): [AUX]GuiExtAuxCheckAuxPath:670: Null anb
E/GPUAUX (24833): [AUX]GuiExtAuxCheckAuxPath:670: Null anb
E/GPUAUX (24833): [AUX]GuiExtAuxCheckAuxPath:670: Null anb

[github-actions]

👋 @berkbuzcu

NOTE: This comment is auto-generated.

Are you sure you have already searched for the same problem?

Some people open new issues but they didn't search for something similar or for the same issue. Please, search for it using the GitHub issue search box or on the official inappwebview.dev website, or, also, using Google, StackOverflow, etc. before posting a new one. You may already find an answer to your problem!

If this is really a new issue, then thank you for raising it. I will investigate it and get back to you as soon as possible. Please, make sure you have given me as much context as possible! Also, if you didn't already, post a code example that can replicate this issue.

In the meantime, you can already search for some possible solutions online! Because this plugin uses native WebView, you can search online for the same issue adding android WebView [MY ERROR HERE] or ios WKWebView [MY ERROR HERE] keywords.

Following these steps can save you, me, and other people a lot of time, thanks!