It would suggest some kind of local memory limitations have been hit and are throwing errors.
The first thing I would look at is what kind of data are you trying to load into the queue and how are you loading it. If you have a very large data set, for example from a massive spreadsheet, just loading it into the database table as-is in one hit could be causing problems for you. Best Practice would be to only store data in the Work Queue that is needed for the work to be done, so remove unnecessary data to be more efficient in your memory and data storage usage. If you are getting errors loading big blocks of data I would recommend instead putting in a loop and adding the data one row at a time (will seem too slow in studio but will run very fast outside of studio).
Other things to look at are the spec of the machines you are using, if developing in a virtual PC is the memory/cpu/etc equivilant to a modern desktop in your organisation or have they under spec'ed it?
Finally, if nothing else solves it and the spec looks fine, Blue Prism has some additional memory logging that you can turn on - it can be done via the resources view in System, there should be instructions of how to do it in the Support Knowledge area, it might give you some clues.
If all the above fails you could raise a support ticket. As always, if you raise a support ticket you should provide all the information about what you have tried so far, you should also provide the relevant log files from both BP session logs with memory logging turned on and also the Windows Event logs showing for when the memory error occured.
------------------------------
Denis Dennehy
Head of Professional Services, EMEA
Blue Prism Ltd
Europe/London
------------------------------
