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

Issue 675131 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Float-cast-overflow in cc::ImageDecodeCacheKey::FromDrawImage

Project Member Reported by ClusterFuzz, Dec 16 2016

Issue description

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5399566020247552

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Float-cast-overflow
Crash Address: 
Crash State:
  cc::ImageDecodeCacheKey::FromDrawImage
  cc::SoftwareImageDecodeCache::GetTaskForImageAndRef
  cc::ImageController::GetTasksForImagesAndRef
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=435261:438085

Minimized Testcase (0.86 Kb): https://cluster-fuzz.appspot.com/download/AMIfv954Obik1G3NGAaCJo8j4KDCvgng3NC8eXx5JDPEpf3MsSDt2BrzWDJYTc4Aei5AXgKBMRt7PGCscXxgXFRgwz_CbPUNsnEZVe8NjBpAPDpH9Dm93OeBABdMVyLyYNPhCpmHXHURSFoL33w_B4_qFpl3AL2cFQ?testcase_id=5399566020247552

Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Cc: msrchandra@chromium.org
Components: Internals>Compositing>Rasterization
Labels: Test-Predator-Correct-CLs
Owner: vmp...@chromium.org
Status: Assigned (was: Untriaged)
Assigning to the concern owner from find it results --
The result is a list of CLs that change the crashed files. 

Author: vmpstr
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/70289fb699a311cf74de0853951145a90c35a5f5
Time: Thu Dec 01 02:33:05 2016
Lines 997 of file tile_manager.cc which potentially caused crash are changed in this cl (frame #3, "cc::TileManager::CreateRasterTask"). 

Files layer_tree_host_impl.cc, software_image_decode_cache.cc are changed in this cl (and is part of stack frame #6, "cc::LayerTreeHostImpl::PrepareTiles")
Minimum distance from crash line to modified line: 0. (file: tile_manager.cc, crashed on: 997, modified: 997). 

Author: vmpstr
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/e556bda6ddeb3e8f8981c5d81aa0d3712c79c1b4
Time: Fri Dec 02 01:51:40 2016
Lines 999-1000 of file tile_manager.cc which potentially caused crash are changed in this cl (frame #3, "cc::TileManager::CreateRasterTask"). 

File image_controller.cc is changed in this cl (and is part of stack frame #2, "cc::ImageController::GetTasksForImagesAndRef")
Minimum distance from crash line to modified line: 0. (file: tile_manager.cc, crashed on: 999, modified: 999).

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

Comment 2 by ClusterFuzz, Dec 22 2016

ClusterFuzz has detected this issue as fixed in range 440242:440280.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5399566020247552

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Float-cast-overflow
Crash Address: 
Crash State:
  cc::ImageDecodeCacheKey::FromDrawImage
  cc::SoftwareImageDecodeCache::GetTaskForImageAndRef
  cc::ImageController::GetTasksForImagesAndRef
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=435261:438085
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=440242:440280

Minimized Testcase (0.86 Kb): https://cluster-fuzz.appspot.com/download/AMIfv954Obik1G3NGAaCJo8j4KDCvgng3NC8eXx5JDPEpf3MsSDt2BrzWDJYTc4Aei5AXgKBMRt7PGCscXxgXFRgwz_CbPUNsnEZVe8NjBpAPDpH9Dm93OeBABdMVyLyYNPhCpmHXHURSFoL33w_B4_qFpl3AL2cFQ?testcase_id=5399566020247552

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

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 3 by ClusterFuzz, Dec 22 2016

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5399566020247552 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Sign in to add a comment