I have a popover with a script trigger on object enter. The script that is triggered calls an FMP URL that runs another script in the same file that goes to a different layout.
I was able to build a brand new file with only the minimal script steps and consistently reproduce the crash.
File attached. UN: Admin, PW:123456
Bare in mind that the example attached is dumbed down to only the items needed to reproduce the issue and do not reflect the full system where the issue was found.
Crash found and reproduced in Windows Server 2016 Datacenter, Intel Xeon CPI E5-2676 v3 @ 2.4 GHz, 4 GB Ram, 64 bit
Also able to reproduce in Windows 10 Pro.
FileMaker Pro Advanced 184.108.40.2063 used in all 4 environments.
Testing on MacOS 10.13.3 and Windows 7 Pro SP1 did not crash.
In all 4 test cases, the file was hosted from a server.
FileMaker Server 220.127.116.116 running on Windows Server 2012 r2 used to test the the Windows Server 2016 Datacenter FMPA client.
FileMaker Server 10.0.3.304 running on MacOS 10.13.3 used to test MacOS, Windows 7 and Windows 10.
When the popover is opened, the OnObjectEnter script trigger calls script "Popover ObObjectEnter".
This script opens an FMP URL to script "Test" in the same file.
Script "Test" goes to a different layout.
The use of Close Popover alone yielded inconsistent results. Seeming to work on occasion, but not in every case.
The addition of a .01 second pause before the Open URL seems to resolve the issue.
When testing in Window Server 2016 Datacenter, FMPA would disappear without any messages, with the exception for 1 time, the "FMPA has stopped working..." dialog appears.
When testing in Window 10 Pro, the standard "FMPA has stopped working..." dialog appeared in every case.