OPCUA Collector - Unhandled error BadOutOfMemory during Publish

We've encountered this error a couple times now and are not sure how to continue debugging to find the root cause.
We've been able to resolve by just restarting the service/the host machine, but are looking to find the root cause to prevent this from repeating.

Can anyone provide context behind this error? Which piece of memory does the error refer to? We've upgraded the resources on the machine so my gut tells me its not about RAM, we also haven't really observed any ram spikes or such, but probably shouldn't discard the possibility.

Is it something within the UA collector service itself?

Another detail is that we have two collector machines for redundancy and they both seem to have failed with this same error around the same time.

Below is the error text for easier copy/pasting if needed:
MESSAGE: PUBLISH #1723087 - Unhandled error BadOutOfMemory during Publish.
EXCEPTION: Opc.Ua.ServiceResultException: BadOutOfMemory
    at Opc.Ua.ClientBase.ValidateResponse(ResponseHeader header)
    at Opc.Ua.SessionClient.EndPublish(IAsyncResult result, UInt32& subscriptionId, UInt32Collection& availableSequenceNumbers, Boolean& moreNotifications, NotificationMessage& notificationMessage, StatusCodeCollection& results, DiagnosticInfoCollection& diagnosticInfos)
    at Opc.Ua.Client.Session.OnPublishComplete(IAsyncResult result)