Unity slows down and becomes essentially unusable when using the Debugger in MonoDevelop and finishing the debugging process with "Step Over" instead of "Step out".

1. What happened

Made a button that has a script attached that prints some text. The method inside the script calls for another method. If a breakpoint is created in the first method and the MonoDevelop is used to attach the script to the Unity process, Unity itself becomes essentially unusable if the debugging mode is finished with "Step over" instead of "Step out". (Please see the attached recording "Debugger Step Over Bug.mov" for correct behavior when using "Step out" and incorrect when using "Step over" as well as some profiler information for a huge spike in CPU usage for scripts during the buggy behaviour).

The issue can only be fixed by de-attaching the script.

Note: The buggy behavior does not seem to occur if the method in the breakpoint does not call for other methods.

Expected result: Unity should continue to run in the same way as if the debugging process was finished with "Step out".

2. How we can reproduce it using the example you attached

• Open the attached project;
• Open the Press.cs script in MonoDevelop;
• Create a breakpoint in Line 7 and attach the script to Unity process;
• Start the Play mode in Unity and press the "Button" in the Game screen;
• Once taken to MonoDevelop, use "Step over" as many times as needed to complete the debugging process;
• Observe the text printing in the Console, but Unity almost freezing.