[heap] don't flush async functions, they may be resumed later

src/heap/objects-visiting-inl.h

Index: src/heap/objects-visiting-inl.h
diff --git a/src/heap/objects-visiting-inl.h b/src/heap/objects-visiting-inl.h
index 4373451e44f45aa86ab14aa7e922974370216b3c..01dd3797753076ab400d504afcfb18c792356315 100644
--- a/src/heap/objects-visiting-inl.h
+++ b/src/heap/objects-visiting-inl.h
@@ -647,9 +647,10 @@ bool StaticMarkingVisitor<StaticVisitor>::IsFlushable(
     return false;
   }
 
-  // We do not (yet?) flush code for generator functions, because we don't know
-  // if there are still live activations (generator objects) on the heap.
-  if (shared_info->is_generator()) {
+  // We do not (yet?) flush code for generator functions, or async functions,

[Hannes Payer (out of office), 2016/05/20 07:13:52]

How about a list of items enumerating what we don't flush with a reason next to
it?

[caitp (gmail), 2016/05/20 07:55:48]

isn't that what this routine is? thats how it looks to me. Reorganizing it might
be a job for someone else

[Hannes Payer (out of office), 2016/05/20 12:00:41]

Ah, async is based on generators. Then the comments makes sense.

+  // because we don't know if there are still live activations
+  // (generator objects) on the heap.
+  if (shared_info->is_resumable()) {
     return false;
   }