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 cleans up iterator's waiters (i.e. `hasNext()` callers) when the channel is closed.
+             * Without this cleanup, waiters will be GC-reacheable even when the channel is already closed and
+             * waiters are successfully resumed.
+             */
             val cont = this.continuation!!
             this.continuation = null
             // Update the `hasNext()` internal result and inform