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

Issue 722065 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
█ msrchandra@chromium.org
█ brettw@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Crash in base::flat_map<std::__1::basic_string<char, std::__1::char_traits<char>, std::__

Project Member Reported by ClusterFuzz, May 13 2017 
Detailed report: https://clusterfuzz.com/testcase?key=5342213235277824

Fuzzer: ochang_domfuzzer
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x0000000004c0
Crash State:
  base::flat_map<std::__1::basic_string<char, std::__1::char_traits<char>, std::__
  base::DictionaryValue::MergeDictionary
  content::BlinkTestController::OnLayoutTestRuntimeFlagsChanged
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=471579:471583

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


Issue filed automatically.

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

Comment 1 by msrchandra@chromium.org, May 15 2017

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

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

Comment 2 by brettw@chromium.org, May 15 2017

Status: Started (was: Assigned)

Comment 3 by brettw@chromium.org, May 15 2017

Cc: brettw@chromium.org
Owner: ----
Status: Available (was: Started)
I looked at this a bit and could not reproduce locally. The code in base::Value and the immediate calling code looks OK to me.

We do MergeDictionary quite a lot, if that was buggy we likely would have noticed it in other places.

It looks like it's got a null pointer and is attempting to dereference it. A wild guess is that the BlinkTestController is being destructed and the IPC message is racing that. I believe if such a pointer is null when this function is called, the crash will look similar.
Project Member

Comment 4 by ClusterFuzz, Jun 15 2017

Status: WontFix (was: Available)
ClusterFuzz testcase 5342213235277824 is flaky and no longer reproduces, so closing issue.

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

Sign in to add a comment