Implement v8::ValueSerializer::Delegate to throw DOMException for DataCloneError.

third_party/WebKit/Source/bindings/core/v8/ExceptionState.h

Index: third_party/WebKit/Source/bindings/core/v8/ExceptionState.h
diff --git a/third_party/WebKit/Source/bindings/core/v8/ExceptionState.h b/third_party/WebKit/Source/bindings/core/v8/ExceptionState.h
index c28703fe5982dcc69652cfab70a5941e2f652e87..2f4ae57bd85ac28a7c603af661e1d02c2e218488 100644
--- a/third_party/WebKit/Source/bindings/core/v8/ExceptionState.h
+++ b/third_party/WebKit/Source/bindings/core/v8/ExceptionState.h
@@ -50,7 +50,6 @@ class ScriptState;
 // with an option to cancel it.  An exception message may be auto-generated.
 // You can convert an exception to a reject promise.
 class CORE_EXPORT ExceptionState {
-    STACK_ALLOCATED();

[jbroman, 2016/09/06 20:39:27]

This change was made because the blink-gc plugin won't permit holding a pointer
to ExceptionState in a class that implements a non-GC interface. This object
doesn't hold pointers to Oilpan objects anyhow, so it doesn't need this.

[haraken, 2016/09/07 00:27:54]

Hmm, I'd like to keep the STACK_ALLOCATED. STACK_ALLOCATED is not only for
oilpan but also for asserting that the class should be used on the stack
(otherwise it's likely to be a bug).

Any idea to restructure the class design around V8ScriptValueSerializer and keep
the STACK_ALLOCATED as is?

[jbroman, 2016/09/07 01:03:34]

Isn't that what DISALLOW_NEW is for? If not, what is the distinction between
STACK_ALLOCATED and DISALLOW_NEW?

I don't think it's very clear whether STACK_ALLOCATED is supposed to mean "this
should be on the stack" or "this is an Oilpan object that only exists on the
stack".

If it is supposed to be the former, then I don't think the restriction that it
only have STACK_ALLOCATED base classes makes sense, because it prevents any pure
interface base class. (And I don't understand the restriction; shouldn't that
restriction be "no base class should be GarbageCollected"?)

V8ScriptValueSerializer could be split into two classes to work around this, but
I'd rather not complicate the code to satisfy blink_gc_plugin, especially when
there's nothing Oilpan-related going on here.

[jbroman, 2016/09/07 01:13:16]

Also, the comment says:

// Classes that contain references to garbage-collected objects but aren't
// themselves garbaged allocated, have some extra macros available which
// allows their use to be restricted to cases where the garbage collector
// is able to discover their references.

So if this is intended also for use on classes that don't use GC objects,
maybe the comment _and_ blink_gc_plugin should be revised?

     WTF_MAKE_NONCOPYABLE(ExceptionState);
 public:
     enum ContextType {