only speculating, but maybe the intense creation of BLOBs is saturating or fragmenting the 32-bit cache management of v15.
it seems like you don't really need to use a BLOB, you could simply call WRITE PICTURE FILE https://doc.4d.com/4Dv15/4D/15.6/WRITE-PICTURE-FILE.301-3818335.en.html since you are on Mac, you could monitor the memory usage of 4D with Activity Monitor. I suspect it keeps on growing until a crash near 4GB. perhaps you could launch a new process and export a few hundred records at a time. every time the process dies, maybe you would see that the memory usage returns to normal. > 2020/04/01 12:19、Robert McKeever via 4D_Tech <4d_tech@lists.4d.com>のメール: > > If (([ScannedDocuments]FileType="JPEG") | ([ScannedDocuments]FileType="JPG")) > PICTURE TO BLOB([ScannedDocuments]FullImage;$MyBlob;".jpg") > Else > PICTURE TO BLOB([ScannedDocuments]FullImage;$MyBlob;".bmp") > End if > BLOB TO DOCUMENT(document;$MyBlob) ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
