UPDATE: probably closing in on the issue.
AndroidEGL is some kind of low-level graphics API used among other things by FAndroidGPUInfo to retrieve graphics hardware capabilities. Both are singletons, AndroidEGL is initialized early during startup. Relevant call is AndroidEGL::InitContexts(), which successfully initializes rendering, shared and single-threaded contexts.
FAndroidGPUInfo is initialized when we first want to query some GPU info, at this point AndroidEGL is already initialized. During initialization it calls AndroidEGL::InitSurface() that eventually comes to
PImplData->eglSurface = eglCreateWindowSurface(PImplData->eglDisplay, PImplData->eglConfigParam,InWindow, NULL);
eglCreateWindowSurface fails with EGL_BAD_ALLOCK, that leads to AndroidEGL::ResetInternal(), which invalidates rendering contexts that have been initialized earlier. The execution countinues, however, all subsequent calls utilizing AndroidEGL return garbage due to invalid rendering context.
So, the question now is, what could cause eglCreateWindowSurface to fail? Khronos docs state: “not enough resources to allocate the new surface”, but that seems unlikely, since as soon as I restart the app, everything works just fine (remember, the crash only happens on first launch).
Also, what is the intended behavior in such case? Seems unlikely, that the execution should resume after AndroidEGL::ResetInternal(), is there some kind of re-initialization procedure that is missing?
Also also, there is a bug report featuring eglCreateWindowSurface with EGL_BAD_ALLOCK (0x3003) error, not sure yet, if this is relevant.