Explain potential memory leak that nulling BufferedChannelIterator.continuation out prevents

Author: qwwdfsad

kotlinx-coroutines-core/common/src/channels/BufferedChannel.kt

@@ -1690,8 +1690,12 @@ internal open class BufferedChannel<E>(
         }
 
         fun tryResumeHasNextOnClosedChannel() {
-            // Read the current continuation and clean
-            // the corresponding field to avoid memory leaks.
+            /*
+             * Read the current continuation and clean the corresponding field to avoid memory leaks.
+             * This nulling out is required to unbind iterator's waiters (e.g. `hasNext()` callers)
+             * from the iterator in case when a channel is closed, continuation is sucessfulluy resumed
+             * with closed token (false|exception), but iterator is still reachable for any reason.
+             */
             val cont = this.continuation!!
             this.continuation = null
             // Update the `hasNext()` internal result and inform