-
Notifications
You must be signed in to change notification settings - Fork 732
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
Ensure we handle cogl functions that return NULL in data_to_cogl_texture #4119
Conversation
Hi, do you have a way of reproducing the issue? |
Not an actual, issue, but should g_clear_error be inside the else block above it? It wouldn't make a difference, but seems to make more sense like that |
@clefebvre Unfortunately I haven't been able to find a way to reproduce it reliably. A few of our users seem to report it happening somewhat randomly although the most common case seems to be after unlocking the screen. Either way, here's a retrace of it happening: #0 cogl_framebuffer_get_winsys (framebuffer=framebuffer@entry=0x0) at ./cogl-framebuffer.c:199 @dalcde Makes sense to me. I've amended the commit to move it inside the else block. |
I should note that the stack trace is from 2.2.16. |
Looks ok to me, tested, no obvious issue. I'm only curious how this never manifested sooner than it did. |
Ensure we handle cogl functions that return NULL in data_to_cogl_texture
I've seen some cases with users experiencing a crash in Cinnamon with a stack trace indicating cogl_famebuffer_allocate was getting called with a null framebuffer. This doesn't fix whatever underlying issue was causing that, but handles the error case to ensure we at least don't crash.