That is not an error I have seen before, it is being thrown by your application/system that Blue Prism is interfacing with or is it being used by Blue Prism itself.
There is a lot of help in the knowledgebase about out of memory errors in the Blue Prism product (usually caused by interfacing with massive collections), you can also investigate memory issue causes by turning on additional logging on a resource in system manager.