Support receiving GrowableObjectArray on native ports

runtime/vm/dart_api_message.cc

Index: runtime/vm/dart_api_message.cc
diff --git a/runtime/vm/dart_api_message.cc b/runtime/vm/dart_api_message.cc
index e7fb7cc3f95d8a693a95aea6a0f7ad3741a4c4f7..c1ff2493c04da815c2702534a214feaedc95c995 100644
--- a/runtime/vm/dart_api_message.cc
+++ b/runtime/vm/dart_api_message.cc
@@ -206,6 +206,24 @@ Dart_CObject* ApiMessageReader::ReadInlinedObject(intptr_t object_id) {
       value->value.as_array.values[i] = ReadObjectRef();
     }
     return value;
+  } else if (class_id == kGrowableObjectArrayCid) {
+    // A GrowableObjectArray is serialized as its length followed by its backing
+    // store. The backing store is an array with a length which might be longer
+    // than the length of the GrowableObjectArray.
+    intptr_t len = ReadSmiValue();
+    Dart_CObject* value = GetBackRef(object_id);
+    ASSERT(value == NULL);
+    // Allocate an empty array for the GrowableObjectArray this will be updated

[Mads Ager (google), 2012/09/10 14:05:05]

this will -> which will

[Søren Gjesse, 2012/09/11 14:36:04]

Done.

+    // to point to the content when the backing store has been deserialized.
+    value = AllocateDartCObjectArray(0);
+    AddBackRef(object_id, value, kIsDeserialized);
+    // Read the content of the GrowableObjectArray.
+    Dart_CObject* content = ReadObjectImpl();
+    ASSERT(content->type == Dart_CObject::kArray);
+    // Make the empty array allocated point to the backing store content.
+    value->value.as_array.length = len;
+    value->value.as_array.values = content->value.as_array.values;

[siva, 2012/09/11 01:46:23]

How will this work if the allocator specified in the constructor for
ApiMessageReader is a malloc allocator?

A free of the returned object will not deallocate the backing store right.

Agreed that we currently only use a zone allocator in the
native message handler and all the test cases and this is
not an issue with a zone allocator.

The ApiMessageHandler class itself doesn't specify that only a zone allocator
should be used.

[Søren Gjesse, 2012/09/11 14:36:04]

We don't really have a way of running through the decoded structure to free the
individual pieces. This was already the case before as the decoded structure can
have cycles and there is no specification of how the various pieces for the
decoded structure are allocated.

I added a comment to the ApiMessageReader saying that the allocator needs to
keep track of data allocated to be able to free it again.

+    return value;
   }
 
   return ReadInternalVMObject(class_id, object_id);