Constant Out Of Memory errors are received in only one environment.
Steps to Reproduce
There is no specific use case to reproduce this behavior.
An issue in the custom application code or rules. It appears that a custom process was pulling back all work objects for a specific class.
While the information in the heap displays a large amount of DirectStreamEncoder objects, this is the result of a listview which is attempting to bring back all work objects for a specific class and is capping out at 10,001 (max for a listview). Note the PAL stats for this - pulling back 10,001 rows (listview max) and 834,457,740 bytes of compressed data (which will be much higher once uncompressed).
0% found this useful