Emulator: glClear:466 GL err 0x502

Question

How to solve the Android Studio 3.0.1 Emulator?

When I start to run the project with virtual device, the error start showing (Emulat

Answer 1

Ya I was faced same problem before. Try this

1. Change the Emulated Performance to Software - GLES 2.0

2. increase the RAM to 3044MB

I hope this will help you.

Answer 2

I resolved it by reinstalling Android Emulator from SDK tool section. Apart from it, also reinstall HAXM with 4GB memory. Then create a new AVD with 2GB RAM and 512 MB VM space.

Answer 3

I was getting this ambiguous error, specifically when glLinkProgram(programId) was being called, and none of these solutions resolved the issue. My problem turned out to be that I didn't correctly set up my shader program. I used glCreateShader(GL_VERTEX_SHADER) for both my vertex and fragment shaders. After I corrected the mistake, the error stopped showing up.

Answer 4

I'm not sure if this counts as an answer or a work around. Yesterday after updating the emulator in Android Studio to version 27.0.2 under SDK Tools I received the exact same error on all of my AVDs. The error appeared on multiple windows laptops I have running Android Studio whenever I started any virtual device in the emulator. The only things I had done to both the laptops in the last day was update Android Studio and I ran a general Windows update.

After some testing I found that if I change the configuration on the virtual devices in the emulator under "Emulated Performance - Graphics" so they use Software GLES 1.1 the error goes away. Before that I had the default setting of Automatic. I tested starting up the virtual devices with the Emulated Performance Graphics setting on Hardware GLES 2.0 and the error came back. No hardware or display drivers were changed on either of my laptops so no idea why the error came up all of a sudden after the Emulator update.

Answer 5

I get this when I have started Firefox and afterwards started the emulator in Adnroid studio, seems that Firefox hogs som resource or that the resource is not sharable. It starts with that the event log spits out:

07:31 Emulator: libpng warning: iCCP: known incorrect sRGB profile

07:31 Emulator: libpng warning: iCCP: known incorrect sRGB profile

Usually ends with Emulator: glClear:470 GL err 0x506 and the emulator dies.

My workaround, dont have firefox open when I start the emulator, opening firefox after doesnt now cause this error

Running system, Win10 latest patches as this date and firefox 60.0.2 (64-bit) and android studio 3.1.4

Answer 6

Updated my video card drivers by downloading them directly from Nvidia, solved the issue. Changing Emulated Performance - Graphics" -> Software - GLES 2.0 will causes the virtual device to lag. Hardware acceleration is the way to go.