BackRenderbuffer path (pepper 3d?) skips a workaround needed on Adreno 4xx/5xx |
|||
Issue descriptionBackRenderbuffer::AllocateStorage does not perform RegenerateRenderbufferIfNeeded, which creates a new renderbuffer on a resize instead of resizing an existing one (workaround: multisample_renderbuffer_resize_emulation). I'm not even sure if this code path is ever hit on Qualcomm devices right now, or if this code path is going to be removed. But it could potentially cause issues.
,
Jun 8 2017
// TODO(kainino): This path will not perform RegenerateRenderbufferIfNeeded
// on devices where multisample_renderbuffer_resize_emulation is needed.
// Thus any code using this path (pepper?) could encounter issues on those
// devices. RenderbufferStorageMultisampleWithWorkaround should be used
// instead, but can only be used if BackRenderbuffer tracks its
// renderbuffers in the renderbuffer manager instead of manually.
// http://crbug.com/731287
,
Jun 11 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 11 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 Deleted