The database and Mac were completely unattended; no user initiated action
or process caused that error. FMPA was running in background while
macOS had Finder in foreground but again, was unattended and not being
used. There were other Apps running in the background also, of course.
There are 2 automated interval scripts that run on the server, but those
are run from Filemaker Server on another Mac on the network and should not
have any effect whatsoever on this Mac, which was the only copy of FMP
running and logged into FMS.
If you would like access to test and reproduce the problem, I am happy to
accomodate this and any efforts to bug fix.
[image: Inline image 1]
On Mon, Mar 13, 2017 at 12:37 PM, TSPigeon <email@example.com>
Thank you for the additional information. I have forwarded your information to Testing and Development for review. I will respond back here when further information is available.
do you have 2 partitions with 10.12.3 and 10.12.4 beta?
if yes - are you running different file systems?
Yes, I had 2 partitions. I have since deleted 10.12.3 due to limited
available space on SSD.
No, same file system HFS+ with Journaling; Case Insensitive.
so you experienced the error on 10.12.4 beta on its partition?
when you erased the other partition's data that might not have freed up any space on the current one if so?
Yes, I experienced it on the 10.12.4 beta partition.
Yes, removing the 10.12.3 partition freed up space but
I can and will see if I can reproduce the problem on the next 10.12.4 build
and run down the disk space again to test Filemaker 15.0.3