Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

eglSwapBuffers failed

Open
#2,004 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, java, kotlin
Domain
mobile-dev

Research direction

The report is a logcat trace from GenericCamera2 on certain Android phones: the preview freezes on bindTextureImage with EGL_BAD_SURFACE while streaming keeps working. The payload names no file or test, so the starting point is the camera preview and EGL surface handling in the library, which needs device-specific knowledge to reproduce. Done would mean a confirmed cause and a fix that keeps the preview alive on the affected devices.

Written by the indexing model from the issue text.

Description

Hi, I'm developing a streaming app using the GenericCamera2 class. However, the preview is frozen with the following error on certain phones. The preview is frozen, but streaming to the server works well. What is the cause? Is there a solution?

ertel.streaming W [SurfaceTexture-1-13786-4] bindTextureImage: clearing GL error: 0x506
libEGL E eglSwapBuffersWithDamageKHRImpl:1361 error 300d (EGL_BAD_SURFACE)
SurfaceManager E eglSwapBuffers failed
....
ertel.streaming W [SurfaceTexture-1-13786-4] bindTextureImage: clearing GL error: 0x506
libEGL E eglSwapBuffersWithDamageKHRImpl:1361 error 300d (EGL_BAD_SURFACE)
SurfaceManager E eglSwapBuffers failed

Dominant language
Kotlin
Stars
3k
Forks
946
Avg merge
4d 6h
Merged PRs (30d)
9

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pedroSG94/RootEncoder

All issues in pedroSG94/RootEncoder

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.