ocr not enough storage is available to process this command

[Dorian (MJT support)]

I just ran 50 cycles on a maximized Chrome window on a dual 4k monitor setup, and even with a tight loop I wasn't able to replicate this. Of course the resource usage was high when performing OCR each time - which is to be expected - but settled down as soon as it completed the 50th cycle.

Oddly enough, it looks like we've only ever had this reported twice before, one of which was someone else using Visual FoxPro. link.

Which version are you using? There was a memory leak identified in the OCR functions, but this was remedied in v14.4.02 in 2017.