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

Fail initialization if the max texture size is insufficient. #1563

Merged
merged 1 commit into from
Aug 10, 2017

Conversation

nical
Copy link
Contributor

@nical nical commented Aug 9, 2017

This works around #1260 (driver issues entry) by gracefully failing the initialization instead of panicking the first time we try to allocate a texture cache page.
This should let us fallback to another compositor backend and more easily identify the issue when it happens.

@nical nical force-pushed the min-max-texture-size branch from 35e8ebd to 8f6cfb3 Compare August 9, 2017 13:55
@nical
Copy link
Contributor Author

nical commented Aug 9, 2017

Moved this sanity check to the beginning of the function to not bother with creating shaders, threads and other resources.

r? @kvark

@kvark
Copy link
Member

kvark commented Aug 9, 2017

Thanks, looking good!
@bors-servo r+

@bors-servo
Copy link
Contributor

📌 Commit 8f6cfb3 has been approved by kvark

@bors-servo
Copy link
Contributor

⌛ Testing commit 8f6cfb3 with merge b86a8eb...

bors-servo pushed a commit that referenced this pull request Aug 9, 2017
Fail initialization if the max texture size is insufficient.

This works around #1260 ([driver issues entry](https://github.com/servo/webrender/wiki/Driver-issues#1260---broken-gl-context-reports-max-texture-size-equal-to-zero)) by gracefully failing the initialization instead of panicking the first time we try to allocate a texture cache page.
This should let us fallback to another compositor backend and more easily identify the issue when it happens.
@bors-servo
Copy link
Contributor

💔 Test failed - status-travis

@kvark
Copy link
Member

kvark commented Aug 9, 2017

@nical y u no compile? :)
all CI is broken

847 | result_tx: result_tx.clone(),
| ^^^^^^^^^ not found in this sco

@nical nical force-pushed the min-max-texture-size branch from 8f6cfb3 to 6e82302 Compare August 9, 2017 15:06
@nical
Copy link
Contributor Author

nical commented Aug 9, 2017

oops, did a last minute change and apparently forgot to build it. This version does build locally now.

@glennw
Copy link
Member

glennw commented Aug 9, 2017

@bors-servo r=kvark,glennw

@bors-servo
Copy link
Contributor

📌 Commit 6e82302 has been approved by kvark,glennw

@bors-servo
Copy link
Contributor

⌛ Testing commit 6e82302 with merge f75908f...

bors-servo pushed a commit that referenced this pull request Aug 9, 2017
Fail initialization if the max texture size is insufficient.

This works around #1260 ([driver issues entry](https://github.com/servo/webrender/wiki/Driver-issues#1260---broken-gl-context-reports-max-texture-size-equal-to-zero)) by gracefully failing the initialization instead of panicking the first time we try to allocate a texture cache page.
This should let us fallback to another compositor backend and more easily identify the issue when it happens.
@bors-servo
Copy link
Contributor

☀️ Test successful - status-travis
Approved by: kvark,glennw
Pushing f75908f to master...

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

Successfully merging this pull request may close these issues.

4 participants