Long running emulator becomes unhealthy - :glCheckFramebufferStatus:733 error 0x500

(2 commenti) (0 reazioni) (0 assegnatari)Python (1745 fork)batch import

help wanted

Metriche repository

Star: (15.739 stelle)
Metriche merge PR: (Merge medio 2g 16h) (4 PR mergiate in 30 g)

Descrizione

🐛 Bug Report

Operating System: Linux 3.10.0-1062.1.1.el7.x86_64 x86_64

Docker compose:

version: '2'

services:
  selenium_hub:
    image: selenium/hub
    restart: unless-stopped
    ports:
      - "4444:4444"

  emulator:
    image: budtmo/docker-android-x86-8.1
    restart: unless-stopped
    privileged: true
    depends_on:
      - selenium_hub
    ports:
      - 6080
      - 5554
      - 5555
    environment:
      - DEVICE=Samsung Galaxy S10
      - CONNECT_TO_GRID=True
      - APPIUM=true
      - SELENIUM_HOST=selenium_hub
      - MOBILE_WEB_TEST=true

Docker Version:
Docker version 19.03.2, build 6a30dfc

Expected Behavior

When I leave my selenium grid with emulators running for longer period they should still be in 'healthy' state

Actual Behavior

I left my emulators up and running overnight (without using them for anything). After 12 hours I can see one of the containers became unhealthy with the following error

[root@uiplinfdoc019 martinco]# docker exec -it docker_emulator_2 tail -f /var/log/supervisor/docker-android.stderr.log
/buildbot/src/android/emu-master-dev/external/qemu/android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glCheckFramebufferStatus:733 error 0x500
/buildbot/src/android/emu-master-dev/external/qemu/android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glCheckFramebufferStatus:733 error 0x500
/buildbot/src/android/emu-master-dev/external/qemu/android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glCheckFramebufferStatus:733 error 0x500
/buildbot/src/android/emu-master-dev/external/qemu/android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glCheckFramebufferStatus:733 error 0x500
/buildbot/src/android/emu-master-dev/external/qemu/android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glCheckFramebufferStatus:733 error 0x500
/buildbot/src/android/emu-master-dev/external/qemu/android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glCheckFramebufferStatus:733 error 0x500
/buildbot/src/android/emu-master-dev/external/qemu/android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glCheckFramebufferStatus:733 error 0x500
/buildbot/src/android/emu-master-dev/external/qemu/android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glCheckFramebufferStatus:733 error 0x500
/buildbot/src/android/emu-master-dev/external/qemu/android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glCheckFramebufferStatus:733 error 0x500
/buildbot/src/android/emu-master-dev/external/qemu/android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glCheckFramebufferStatus:733 error 0x500

System resources does not seem to be fully depleted.

Guida contributor

Direzione di ricerca: Indagare sulla causa principale dell'errore glCheckFramebufferStatus 0x500 che si verifica dopo l'esecuzione prolungata degli emulatori. L'errore appare nel file GLESv2Imp.cpp all'interno del livello di traduzione grafica dell'emulatore Android. Cercare potenziali perdite di memoria o esaurimento delle risorse nell'emulazione OpenGL, possibilmente legate a oggetti framebuffer non rilasciati correttamente nel tempo. Rivedere la configurazione del controllo di integrità di Docker e considerare se il driver grafico dell'emulatore necessiti di un reset periodico.
Tech stack: docker
Dominio: infrastructure
Tipo issue: Bug
Difficoltà: 3
Tempo stimato: Mezza giornata
Stato attività: Attiva
Chiarezza: Chiara
Prerequisiti: DockerAndroid emulator basics
Adatta ai principianti: 30