New issue
Advanced search Search tips

Issue 861522 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Jul 9
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in content::GetRenderStyleForStrike

Project Member Reported by ClusterFuzz, Jul 7

Issue description

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

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

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  content::GetRenderStyleForStrike
  content::RendererBlinkPlatformImpl::SandboxSupport::GetWebFontRenderStyleForStri
  blink::FontPlatformData::QuerySystemRenderStyle
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=572538:572540

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Jul 7

Labels: OS-Chrome
Project Member

Comment 2 by ClusterFuzz, Jul 7

Labels: Fuzz-Blocker ReleaseBlock-Beta M-69
This crash occurs very frequently on linux platform and is likely preventing the fuzzer ifratric-browserfuzzer-v3 from making much progress. Fixing this will allow more bugs to be found.

Marking this bug as a blocker for next Beta release.

If this is incorrect, please add ClusterFuzz-Wrong label and remove the ReleaseBlock-Beta label.
Project Member

Comment 3 by ClusterFuzz, Jul 7

Components: Internals>Core
Labels: Test-Predator-Auto-Components
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 4 by ClusterFuzz, Jul 7

Labels: Test-Predator-Auto-Owner
Owner: drott@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/b993e42cacf1ed4454b4df62dfacf8eee2bec869 (Move Blink Sandbox IPC to Mojo Calls).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Status: Started (was: Assigned)
Project Member

Comment 7 by bugdroid1@chromium.org, Jul 9

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

commit e2330adba39d468d6e098a04107f3a15060061a4
Author: Dominik Röttsches <drott@chromium.org>
Date: Mon Jul 09 10:09:07 2018

Do not access font family name in logging when null

Bug:  861522 
Change-Id: Id3f51858a742b3d578e294e9f8a2e0024eb35d57
Reviewed-on: https://chromium-review.googlesource.com/1128749
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573260}
[modify] https://crrev.com/e2330adba39d468d6e098a04107f3a15060061a4/content/child/child_process_sandbox_support_impl_linux.cc

Status: Fixed (was: Started)
Project Member

Comment 9 by ClusterFuzz, Jul 9

ClusterFuzz has detected this issue as fixed in range 572938:572949.

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

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

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  content::GetRenderStyleForStrike
  content::RendererBlinkPlatformImpl::SandboxSupport::GetWebFontRenderStyleForStri
  blink::FontPlatformData::QuerySystemRenderStyle
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=572538:572540
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=572938:572949

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

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 10 by ClusterFuzz, Jul 9

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

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

Sign in to add a comment