Endless spam in emulator syslog (eglCodecCommon: setVertexArrayObject: set vao)

[matkoniecz]

TO REPRODUCE THE ISSUE, FOLLOW THESE STEPS:

• Installed Android Studio
• Created emulated device with Android Studio
• Installed StreetComplete (this app is using tangram-es)

RESULT:

2020-10-21 21:37:43.819 7274-7337/de.westnordost.streetcomplete.debug D/eglCodecCommon: setVertexArrayObject: set vao to 1 (1) 4 7

spamming syslog

See https://github.com/westnordost/StreetComplete/issues/2187 for full listing from a single milisecond

EXPECTED RESULT:

I have no insane syslog spam that makes debugging of an actual problem impossible.

ENVIRONMENT:

• Tested Android 10 emulator running on Ubuntu 20.04 and on Windows 10.
• 0.13 - https://github.com/westnordost/StreetComplete/blob/master/app/build.gradle.kts#L170

OTHER:

I have not reproduced it on physical devices that I own.

I have no idea how to eliminate it and what kind of debugging would be useful, but I would be happy to perform it if directed.

https://hastebin.com/ixikosofuf.apache

[matteblair]

Yikes, that definitely shouldn't happen. Seems like it's printing one of these for every VAO that's drawn, which is quite a lot.

I believe eglCodecCommon is Android platform code, so this might just be a bug in the emulator that's out of our control. However, I'll see if we can do anything to suppress these logs.

[matkoniecz]

bug in the emulator

If that is the case - if anyone knows what is the workaround it also would be valuable.

[westnordost]

@matkoniecz Which processor architecture does your emulated virtual device use? Usually it is the x86 architecture (for performance reasons). Actual devices usually use the arm64-v8 processor architecture. For each architecture, a different binary is used, maybe you can try if it is reproducible on an emulator using the arm64-v8 architecture.

[matteblair]

Update: I'm able to reproduce this issue by running our Android demo app in an emulator on macOS. I used an x86 Pixel 2 API 29 (Android 10) image. The issue does not occur when using images with earlier Android versions, so this means that something changed with the Android emulator - not Tangram.

That said, it's still possible that we could find a workaround to include in Tangram, for developer convenience.

[matkoniecz]

Both x86 Android 9 and x86 Android 10 and exhibit this problem for me.

Android Studio offers Android 7.1.1 arm64-v8 image and no later ones. I am downloading it right now and test whatever deeper downgrade and/or arm64-v8 is sufficient as a workaround.