Step into in debugger pegs server CPU

Discussion created by Smef on Feb 9, 2016
Latest reply on Feb 10, 2016 by Smef



I've found an issue where the "step into" button to step into a script causes FileMaker Server's CPU usage to max out for 10-20 seconds while the step-into is running until the step into is complete and the "stepped-into" script is displayed with the debugger on the first step of the stepped-into script. Once the step into completes the CPU usage drops back down to normal levels. While this is happening FileMaker becomes unresponsive.


Product and version FileMaker Server and FileMaker Pro Advanced 14.0.4

OS and version - Server is on Win 2012 R2 and Pro Advanced is Mac OS 10.11.3

Browser and version (for WebDirect only)

Hardware - Server is AWS virtual machine, Pro is on a 2013 iMac


How to replicate - It's not reliably triggered, but using the "step-into" button can cause FMP to become unresponsive and the server CPU to max out until the step-into is able to resolve and show the script being stepped into

Workaround (if any) - none, but running the script is fine - it's only when running the debugger and stepping into the script that the problem shows up