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

Issue 728956 link

Starred by 1 user
Status: WontFix
Owner:
yukishiino@chromium.org
Closed: Jul 2017
Cc:
█ msrchandra@chromium.org
dcheng@chromium.org
lfg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

CHECK failure: !context.IsEmpty() in LocalWindowProxy.cpp

Project Member Reported by ClusterFuzz, Jun 2 2017 
Detailed report: https://clusterfuzz.com/testcase?key=4997355245142016

Fuzzer: ochang_domfuzzer
Job Type: linux_asan_chrome_mp
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !context.IsEmpty() in LocalWindowProxy.cpp
  
Sanitizer: address (ASAN)

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


Issue filed automatically.

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

Comment 1 by msrchandra@chromium.org, Jul 4 2017

Cc: msrchandra@chromium.org
Labels: M-60 Test-Predator-Wrong
Owner: dcheng@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL did not provide any possible suspects.
Using Code Search for the file, "LocalWindowProxy.cpp" assigning to the concern owner from GIT Blame.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/690c3cf203b94623e5adbece7d6b4afc3501cd94

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

Comment 2 by dcheng@chromium.org, Jul 7 2017

Cc: dcheng@chromium.org
Components: Blink>Bindings
Owner: yukishiino@chromium.org
It seems that context initialization is failing somehow?

Comment 3 by yukishiino@chromium.org, Jul 10 2017

Labels: -Pri-1 Pri-2
Status: WontFix (was: Assigned)
This is a stack overflow, and we're intentionally crashing in that case.
►

Sign in to add a comment