Finite loop detector is triggered in mouseDragged but not in draw when calling the same code

The KA finite loop detector misfires when a CPU intensive function is invoked from mouseDragged. Invoking the same function from draw is fine (as if anything associated with the loop detector is "fine").

A simple test program is at https://www.khanacademy.org/computer-programming/wat4/5728076905971712 This is using Chrome on LinuxMint (Ubuntu).

Reproduce the linked program in Chrome on LinuxMint and compare the finite loop detector behavior when the CPU-intensive function runs from mouseDragged versus draw. Trace the detector entry points for both callbacks; done means the same code is handled consistently without a false finite-loop report.

Written by the indexing model from the issue text.