New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 685128 link

Starred by 1 user
Status: Duplicate
Owner:
█ roc...@chromium.org
please use my google.com address
Closed: Jan 2017
Cc:
sadrul@chromium.org
█ msrchandra@chromium.org
rmcilroy@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Crash in ui::ClientGpuMemoryBufferManager::AllocateGpuMemoryBufferOnThread

Project Member Reported by ClusterFuzz, Jan 25 2017 
Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5818506890444800

Fuzzer: mbarbella_js_mutation_layout
Job Type: linux_asan_chrome_v8_ignition
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  ui::ClientGpuMemoryBufferManager::AllocateGpuMemoryBufferOnThread
  base::debug::TaskAnnotator::RunTask
  base::MessageLoop::RunTask
  
Sanitizer: address (ASAN)

Regressed: V8: 42611:42615

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv96MQoXZX7h_bOG9YQftp-y-omgsVKTtetYl8pE59SkPSbx_IeaaVgFjJ01hH9kUQRMNQUYy-Vt8pLiq05Iq8khXEJRFD8T6CM79aYDNot98VLjNPAp93chDtZyV50GkKqziVqB9Ji3pp-mJqVKcVYbioog30COPX-0P1xUjOAE8QfowgmRQGdg_oD9T9T5XEb63Xt5edYresQKQjiwxmFWGl19NHZoXHUF99OqS_WsdAY6gODsVp7b9fh9Qro7R5fTzOnp6e_nDWGQR9P-wv-O7YeHzwXyldfQQ1wCAN6Z2uZrgeZs5T8jPyX9q69BoMFCLxX6P1ovQ5gMoI8fTS1PXGfrxUYB3mEiU3EhQwjEb4n7gYW4?testcase_id=5818506890444800


Additional requirements: Requires Gestures

Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

Comment 1 by msrchandra@chromium.org, Jan 25 2017

Cc: msrchandra@chromium.org
Labels: Test-Predator-Wrong
Owner: roc...@chromium.org
Status: Assigned (was: Untriaged)
Find it and CL did not provide any possible suspects.
Using Code Search for the file, "client_gpu_memory_buffer_manager.cc" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/55cddd7d290b2fc35dcb4be033f8cd91424596ba

@rockot -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Comment 2 by roc...@chromium.org, Jan 25 2017

Cc: sadrul@chromium.org
So here's an interesting one, sadrul@. It looks like a null |wait| in AllocateGpuMemoryBufferOnThread, but as far as I can tell that is impossible. Any ideas?

Comment 3 by sadrul@chromium.org, Jan 25 2017 

Maybe the crash is running this version of the code: https://chromium.googlesource.com/chromium/src/+/d0e46de3ff797f53376fa63297a5d41241568fdf/services/ui/public/cpp/gpu/client_gpu_memory_buffer_manager.cc? In which case, line 85 is accessing |gpu_|. If that's the case, then your latest CL will have fixed that, right?

Comment 4 by roc...@chromium.org, Jan 25 2017 

Indeed that's possible and I suppose likely. I hadn't considered that. :)

Seems odd that there is no information in the clusterfuzz report regarding which revision of chromium this was running.

Comment 5 by roc...@chromium.org, Jan 25 2017

Mergedinto: 684540
Status: Duplicate (was: Assigned)
►

Sign in to add a comment