Quieten CBDATA 'leak' messages

The majority being reported were false-positive as
cbdataReferenceValidDone() clearing the valid flag before the lock.

diff --git a/src/cbdata.cc b/src/cbdata.cc
index c125eb03f0a8cdb82d35ec3f10a38fa6601c7992..8c149ec790c4e5014ff0bd9b26f388c3ae394ddf 100644 (file)
--- a/src/cbdata.cc
+++ b/src/cbdata.cc
@@ -409,7 +409,7 @@ cbdataInternalUnlock(const void *p)
 
     if (c->valid) {
 #if USE_CBDATA_DEBUG
-        debugs(45, DBG_IMPORTANT, "CBDATA memory leak. cbdata=" << p << " " << file << ":" << line);
+        debugs(45, 3, "CBDATA valid with no references ... cbdata=" << p << " " << file << ":" << line);
 #endif
         return;
     }