This also impacts chrome.debugger.sendCommand. If the result has too much nesting then the API fails silently.

This is both due to json_parser.cc have a recursion limit of 100, and the IPC serialization code having a similar limit.

Fix at https://codereview.chromium.org/2570113002. I wonder if this can have any security implications though.

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

commit 383b174a3c321fc6963c50515745d559222ba709
Author: joaodasilva <joaodasilva@chromium.org>
Date: Tue Jan 10 09:55:36 2017

Increase the depth limit of JSONParser and IPC serialization from 100 to 200.

This impacts extension APIs and the debug protocol. Some webpages
have over 100 levels of nested elements. Some internal representations
further use 2 levels per node to represent the DOM data (e.g. one
DictionaryValue for the node and a ListValue containing the children.)

The affected APIs fail silently when this limit is reached.

Percentiles over ~90M random pages:
  Max depth: go/html-depth
  Iframes found at depth: go/html-iframe-depth

To support 99.9% of pages we need (62 + 35) * 2 == 194 levels of nesting.

BUG= 673263 

Review-Url: https://codereview.chromium.org/2570113002
Cr-Commit-Position: refs/heads/master@{#442542}

[modify] https://crrev.com/383b174a3c321fc6963c50515745d559222ba709/base/json/json_parser.cc
[modify] https://crrev.com/383b174a3c321fc6963c50515745d559222ba709/base/json/json_parser_unittest.cc
[modify] https://crrev.com/383b174a3c321fc6963c50515745d559222ba709/components/safe_json/android/java/src/org/chromium/components/safejson/JsonSanitizer.java
[modify] https://crrev.com/383b174a3c321fc6963c50515745d559222ba709/components/safe_json/json_sanitizer_unittest.cc
[modify] https://crrev.com/383b174a3c321fc6963c50515745d559222ba709/ipc/ipc_message_utils.cc