Closed
Bug 1184327
Opened 9 years ago
Closed 9 years ago
Depth buffer should not be cleared in GL compositor
Categories
(Core :: Graphics, defect)
Core
Graphics
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: acomminos, Assigned: acomminos)
References
Details
Attachments
(1 file)
2.15 KB,
patch
|
Details | Diff | Splinter Review |
apitrace reports the following warning:
> Failed to fast clear depth due to scissor being enabled. Possible 5% performance win if avoided.
I discussed this with :mattwoodrow in person and we agreed that it doesn't make any sense for the GL compositor to clear the depth buffer.
Assignee | ||
Comment 1•9 years ago
|
||
Talos try push for possible OS X 10.10 regression: https://treeherder.mozilla.org/#/jobs?repo=try&revision=a36de385f031
Attachment #8634405 -
Flags: review?(mstange)
Assignee | ||
Comment 2•9 years ago
|
||
Comment on attachment 8634405 [details] [diff] [review] Disable GL scissor test before clearing. This shouldn't be necessary with the fix for bug 1184534.
Attachment #8634405 -
Flags: review?(mstange)
Assignee | ||
Comment 3•9 years ago
|
||
Closing as wontfix- GLX defaults to a GLX_DEPTH_SIZE of 0, falling back to FBConfigs with larger depth sizes if necessary. If we're getting a depth buffer at all, it's because we couldn't find an FBConfig without one.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•