Chromium floods console with errors about content::BrowserGpuMemoryBufferManager |
||||||||
Issue descriptionthousands of times this: [42082:29955:0523/135702:5710186406706:ERROR:browser_gpu_memory_buffer_manager.cc(602)] Not implemented reached in void content::BrowserGpuMemoryBufferManager::HandleCreateGpuMemoryBufferFromClientIdOnIO(content::BrowserGpuMemoryBufferManager::CreateGpuMemoryBufferFromClientIdRequest *) seems like at least once every frame?
,
May 23 2016
This is actually in Chromium.app too.
,
May 23 2016
Thanks - will take a look. Don't remember seeing this in Chromium.app - maybe something changed recently.
,
May 23 2016
This happens on both GPU and SW raster. Looks like it was introduced in the following range: https://chromium.googlesource.com/chromium/src/+log/4db57d47a591423e7ecaf1bc965d35f094250e35..d429e25851e808a426a8a692525987f3da008559 Suspecting crrev.com/1984873002 as this dealt with GPU Memory Buffers. Erik, can you take a look? Thanks! This range is after the M-52 branch point, changing to ReleaseBlock-Beta for M-53.
,
May 23 2016
,
May 23 2016
+ccameron
,
May 23 2016
,
May 23 2016
Right. The implementation is still in review: https://codereview.chromium.org/1993333002/ Let me revert my CL for now.
,
May 25 2016
,
May 25 2016
,
May 25 2016
Sorry, this was my fault -- I didn't remember that the spamming was still there. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by esprehn@chromium.org
, May 23 2016