New issue
Advanced search Search tips

Issue 614155 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug



Sign in to add a comment

Chromium floods console with errors about content::BrowserGpuMemoryBufferManager

Project Member Reported by esprehn@chromium.org, May 23 2016

Issue description

thousands 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?
 
Labels: -Pri-3 Pri-2
This is actually really bad, it makes the scores in Content Shell be bad because we're causing tons of IO to spam the console.
Labels: -Pri-2 ReleaseBlock-Beta M-52 Pri-1
Summary: Chromium floods console with errors about content::BrowserGpuMemoryBufferManager with Ganesh turned on (was: Content Shell floods console with errors about content::BrowserGpuMemoryBufferManager with Ganesh turned on)
This is actually in Chromium.app too.

Comment 3 by ericrk@chromium.org, May 23 2016

Thanks - will take a look. Don't remember seeing this in Chromium.app - maybe something changed recently.

Comment 4 by ericrk@chromium.org, May 23 2016

Cc: ericrk@chromium.org
Components: -Internals>GPU>Rasterization Internals>GPU>Internals
Owner: erikc...@chromium.org
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.

Comment 5 by ericrk@chromium.org, May 23 2016

Labels: -M-52 M-53
Cc: ccameron@chromium.org
+ccameron

Comment 7 by ericrk@chromium.org, May 23 2016

Summary: Chromium floods console with errors about content::BrowserGpuMemoryBufferManager (was: Chromium floods console with errors about content::BrowserGpuMemoryBufferManager with Ganesh turned on)
Right. The implementation is still in review:
https://codereview.chromium.org/1993333002/

Let me revert my CL for now.
Status: fi (was: Assigned)
Status: Fixed (was: fi)
Sorry, this was my fault -- I didn't remember that the spamming was still there.

Sign in to add a comment