New issue
Advanced search Search tips

Issue 773254 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Abrt in blink::RecordToBitmap

Project Member Reported by ClusterFuzz, Oct 10 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5631346562301952

Fuzzer: inferno_twister
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900000001
Crash State:
  blink::RecordToBitmap
  blink::DrawingDisplayItem::Equals
  blink::PaintController::CheckUnderInvalidation
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=419755:419848

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5631346562301952

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Project Member

Comment 1 by ClusterFuzz, Oct 10 2017

Components: Blink>Paint
Labels: Test-Predator-AutoComponents
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Oct 10 2017

Labels: Test-Predator-AutoOwner
Owner: pdr@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/d87b686a8b9e559c1f39d8f5cf445c079773e288 (Add "threaded scrolling disabled" main thread scrolling reason [spv2]).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

Comment 3 by pdr@chromium.org, Oct 10 2017

Cc: pdr@chromium.org
Owner: wangxianzhu@chromium.org
This is in CheckUnderInvalidation. Xianzhu, could you take a look at this?

Comment 4 by pdr@chromium.org, Oct 10 2017

Labels: -Pri-1 Pri-2
Not a P1 as this only occurs in under invalidation checking logic.
Project Member

Comment 5 by bugdroid1@chromium.org, Oct 10 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/cbbdc4c297983084da57c445bf442296f5379b5e

commit cbbdc4c297983084da57c445bf442296f5379b5e
Author: Xianzhu Wang <wangxianzhu@chromium.org>
Date: Tue Oct 10 22:34:10 2017

Limit bounds when comparing bitmaps of DrawingDisplayItems to prevent OOM

The changed code is used only when blink feature
PaintUnderInvalidationChecking is enabled.

Bug:  773254 
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I2c9f682cb5c59e8b2c7db87d6bb8a64d55bbf2d2
Reviewed-on: https://chromium-review.googlesource.com/710055
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#507798}
[add] https://crrev.com/cbbdc4c297983084da57c445bf442296f5379b5e/third_party/WebKit/LayoutTests/paint/invalidation/under-invalidation-checking-oom.html
[modify] https://crrev.com/cbbdc4c297983084da57c445bf442296f5379b5e/third_party/WebKit/Source/platform/graphics/paint/DrawingDisplayItem.cpp

Status: Fixed (was: Assigned)
Project Member

Comment 7 by ClusterFuzz, Oct 11 2017

ClusterFuzz has detected this issue as fixed in range 507774:507876.

Detailed report: https://clusterfuzz.com/testcase?key=5631346562301952

Fuzzer: inferno_twister
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900000001
Crash State:
  blink::RecordToBitmap
  blink::DrawingDisplayItem::Equals
  blink::PaintController::CheckUnderInvalidation
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=419755:419848
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=507774:507876

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5631346562301952

See https://github.com/google/clusterfuzz-tools 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 8 by ClusterFuzz, Oct 11 2017

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

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components
Labels: -Test-Predator-AutoOwner Test-Predator-Auto-Owner

Sign in to add a comment