[K/N] Fix a race on mark queue destruction in CMS GC

Merge-request: KT-MR-14076

kotlin-native/runtime/src/gc/cms/cpp/ConcurrentMark.cpp

@@ -78,11 +78,9 @@ void gc::mark::ConcurrentMark::runMainInSTW() {
         }
     } while (!tryTerminateMark(everSharedBatches));
 
-    for (auto& thread : *lockedMutatorsList_) {
+    // By this point mutator mark queues may not be populated anymore.
-        thread.gc().impl().gc().mark().markQueue().destroy();
+    // However, some threads may still try to enqueue a marked object, before they observe the barrier disablement.
-    }
+    // Thus, mark queue destruction takes place only later below.
-
-    endMarkingEpoch();
 
     gc::processWeaks<DefaultProcessWeaksTraits>(gcHandle(), mm::SpecialRefRegistry::instance());
 
@@ -94,6 +92,11 @@ void gc::mark::ConcurrentMark::runMainInSTW() {
     }
 
     barriers::disableBarriers();
+
+    for (auto& thread : *lockedMutatorsList_) {
+        thread.gc().impl().gc().mark().markQueue().destroy();
+    }
+    endMarkingEpoch();
 }
 
 void gc::mark::ConcurrentMark::runOnMutator(mm::ThreadData&) {