Remove clear function from RefCountContext

Clear method exposed by RefCountContext class could possibly cause a
race condition when misused.

Author: kswiecicki

scripts/templates/valddi.cpp.mako

@@ -221,13 +221,11 @@ namespace ur_validation_layer
     }
 
     ${x}_result_t context_t::tearDown() {
-        ${x}_result_t result = ${X}_RESULT_SUCCESS;
-
         if (enableLeakChecking) {
             getContext()->refCountContext->logInvalidReferences();
-            getContext()->refCountContext->clear();
         }
-        return result;
+        
+        return ${X}_RESULT_SUCCESS;
     }
 
 } // namespace ur_validation_layer

source/loader/layers/validation/ur_leak_check.hpp

@@ -109,7 +109,7 @@ struct RefCountContext {
         // No more active adapters, so any references still held are leaked
         if (adapterCount == 0) {
             logInvalidReferences();
-            clear();
+            counts.clear();
         }
     }
 
@@ -133,8 +133,6 @@ struct RefCountContext {
         updateRefCount(handle, REFCOUNT_CREATE_OR_INCREASE, isAdapterHandle);
     }
 
-    void clear() { counts.clear(); }
-
     template <typename T> bool isReferenceValid(T handle) {
         std::unique_lock<std::mutex> lock(mutex);
         auto it = counts.find(static_cast<void *>(handle));

source/loader/layers/validation/ur_valddi.cpp

@@ -11182,13 +11182,11 @@ ur_result_t context_t::init(ur_dditable_t *dditable,
 }
 
 ur_result_t context_t::tearDown() {
-    ur_result_t result = UR_RESULT_SUCCESS;
-
     if (enableLeakChecking) {
         getContext()->refCountContext->logInvalidReferences();
-        getContext()->refCountContext->clear();
     }
-    return result;
+
+    return UR_RESULT_SUCCESS;
 }
 
 } // namespace ur_validation_layer