Syntergy.Replicator.Service.exe writes a lot of entries to the ULS log (4272348)

Symptom

The SharePoint ULS logs contain a lot of entries from the Syntergy.Replicator.Service.exe service. These entries look like any of the following:

An SPRequest object was reclaimed by the garbage collector instead of being explicitly freed.  To avoid wasting system resources, dispose of this object or its parent (such as an SPSite or SPWeb) as soon as you are done using it.  Allocation Id: {C8F86994-E621-408C-B0B4-7FB431CC1750}  To determine where this object was allocated, create a registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\HeapSettings.  Then create a new DWORD named SPRequestStackTrace with the value 1 under this key.

ERROR: request not found in the TrackedRequests. We might be creating and closing webs on different threads. ThreadId = 2, Free call stack =    at Microsoft.SharePoint.SPRequestManager.Release(SPRequest request)     at Microsoft.SharePoint.SPWeb.Invalidate()     at Microsoft.SharePoint.SPWeb.Close()     at Microsoft.SharePoint.SPWeb.Dispose()     at Syntergy.Replicator.Web.Dispose(Boolean Disposing)     at Syntergy.Replicator.BaseObject.Finalize()  , Allocation call stack (if present) null

Monitorable Potentially excessive number of SPRequest objects (9) currently unreleased on thread 14.  Ensure that this object or its parent (such as an SPWeb or SPSite) is being properly disposed. This object is holding on to a separate native heap. Allocation Id for this object: {AB5B41C4-F760-46FE-A442-985C75856CD4} Stack trace of current allocation:    at Microsoft.SharePoint.SPRequestManager.Add(SPRequest request, Boolean shareable)     at Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity(Boolean bNotGlobalAdminCode, String strUrl, Boolean bNotAddToContext, Byte[] UserToken, String userName, Boolean bIgnoreTokenTimeout, Boolean bAsAnonymous)     at Microsoft.SharePoint.SPWeb.InitializeSPRequest()     at Microsoft.SharePoint.SPWeb.EnsureSPRequest()     at Microsoft.SharePoint.SPWeb.get_Request()     at Microsoft.SharePoint.SPWeb.SetMondoProcHint(Int32 hint)     at Microsoft.SharePoint.SPSite.OpenWeb(Guid gWebId, Int32 mondoHint)     at Microsoft.SharePoint.SPSite.OpenWeb(Guid gWebId)     at Syntergy.Replicator.WebCollection.Add(Guid WebID)     at Syntergy.Replicator.WebCollection.GetWebByID(Guid WebID)     at Syntergy.Replicator.ReplicationPackage.get_SourceWeb()     at Syntergy.Replicator.ReplicationPackage.get_ReplicationMap()     at Syntergy.Replicator.OutboundReplicationQueueItem.Process(ReplicationQueueItem PreviousItem)     at Syntergy.Replicator.ReplicationQueue.ProcessQueue(DateTime QueueItemCreatedDateThreshold)     at Syntergy.Replicator.Server.ReplicateOutbound(ReplicationMapFamily MapFamily, Guid ReplicationMapFamilyId, Guid SiteId, DateTime QueueItemCreatedDateThreshold)     at Syntergy.Replicator.ReplicationEngine.WorkItems.OutboundWorkItem.processServer(Server server, ReplicationMapFamily MapFamily, DateTime QueueItemCreatedDateThreshold)     at Syntergy.Replicator.ReplicationEngine.WorkItems.OutboundWorkItem.Process()     at Syntergy.Replicator.ReplicationEngine.WorkerThread.MainWorkerThread()     at System.Threading.ThreadHelper.ThreadStart_Context(Object state)     at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)     at System.Threading.ThreadHelper.ThreadStart()

To resolve this issue, increase the threshold for reporting recycled threads as follows:

1. Add a key to the registry named "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\HeapSettings".
2. Add a DWORD value to the key named LocalSPRequestWarnCount. Give it a value of 80 (decimal). You may need to increase this value 

See http://msdn.microsoft.com/en-us/library/aa973248%28v=office.12%29.aspx for further details.