Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

framebuffer not visible #983

Closed
gapid-user opened this issue Aug 24, 2017 · 4 comments
Closed

framebuffer not visible #983

gapid-user opened this issue Aug 24, 2017 · 4 comments

Comments

@gapid-user
Copy link

first error from log:

gapis: Framebuffer error: No format set (3 times)

Then a bunch of command errors

@gapid-user
Copy link
Author

I also noticed that there are two contexts from two different threads. One thread called "Renderthread", I don't know what that is. Maybe that's related to the problem.

@ben-clayton
Copy link
Contributor

ben-clayton commented Aug 24, 2017

Hi @gapid-user (nice name!),
Would you be happy sharing the .gfxtrace file with me?

ben-clayton added a commit to ben-clayton/gapid that referenced this issue Aug 24, 2017
This logic was added to handle cases where tracing missed the context creation. It got broken over time.

Fixes: google#983
@ben-clayton
Copy link
Contributor

Thank you @gapid-user,

So it looks like we never saw the call to eglCreateContext. We've seen this happen on an oldish Samsung device before, and so we added some code that tries to recover from missing context. Unfortunately this path had a bug that made things explode. Just to confirm - is this a galaxy tab 2?

There's another issue with this trace where pre-compiled shaders were not disabled. We've recently fixed an issue where this wasn't disabled by default.

I'm planning on pushing out a release in the next few working days. Both of these issues should be fixed for that version.

Thanks again,
Ben

@gapid-user
Copy link
Author

no this is from a new galaxy xcover 3 phone (model SM-G389F).. my old galaxy tab 2 doesn't get recognized at all by GAPID (in android studio it works fine)

ben-clayton added a commit that referenced this issue Aug 25, 2017
This logic was added to handle cases where tracing missed the context creation. It got broken over time.

Fixes: #983
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants