Oilpan: Change the name of the finalization method that can be
overridden for explicit destructor dispatching.

The |finalize| name is too short and makes sense in other places
in the code. We rarely need to override finalizeGarbageCollectedObject
so it is fine that the method name is long.

Concretely, fileapi Stream has a finalize method that currently
gets called instead of the destructor. That leads to crashes because
the Stream destructor is not called and therefore the Stream is
no unregistered as a ContextLifecycleObserver and a call is made
on the already dead stream when the Document dies.

R=erik.corry@gmail.com, haraken@chromium.org, oilpan-reviews@chromium.org, tkent@chromium.org, zerny@chromium.org
BUG=352755

Review URL: https://codereview.chromium.org/199273005

git-svn-id: svn://svn.chromium.org/blink/trunk@169548 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: [JsDocValidator] Fix checking of receivers specified as arguments

r169450 has resulted in multiple failures of existing code where functions
annotated with @this are passed as arguments along with their receivers.

The cases include:
- Array.prototype.forEach and other iteration-with-callback methods.
- RemoteObject.prototype.callFunction[JSON], whose functionDeclaration
  can be evaluated on any Object (but expect a certain type thereof).
- WebInspector.Object.prototype.{add,remove}EventListener, which accepts
  the callback receiver as its third argument.

This patch introduces receiver specification detection in these cases,
or resorts to IGNORE in ambiguous situations.

R=aandrey, sergeyv, vsevik
NOTRY=true

Review URL: https://codereview.chromium.org/203443010

git-svn-id: svn://svn.chromium.org/blink/trunk@169549 bbb929c8-8fbe-4397-9dbb-9b2b20218538