The problem still reproduces with the latest WIP build:
SystemInfo
Rhino 9 SR0 2026-7-28 (Rhino 9 BETA, 9.0.26209.18303, Git hash:master @ 6df6360b2b50949f0737260b2d7af95d8142d1ac)
License type: Commercial, build 2026-07-28
License details: Cloud Zoo
Expires on: 2026-09-11
Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 32GB)
.NET 10.0.10
Computer platform: LAPTOP - Plugged in [79% battery remaining]
Non-hybrid graphics configuration using DirectX
Primary display: NVIDIA GeForce RTX 3080 Laptop GPU (NVidia) Memory: 8GB, Driver date: 5-19-2026 (M-D-Y). DirectX(11)
> Integrated accelerated graphics device with 1 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Secondary graphics devices.
Intel(R) UHD Graphics (Intel) Memory: 1GB, Driver date: 12-23-2021 (M-D-Y).
> Integrated graphics device with 4 adapter port(s)
- Secondary monitor is laptop’s integrated screen or built-in port
- Secondary monitor attached to adapter port #1
Intel(R) UHD Graphics (Intel) Memory: 1GB, Driver date: 12-23-2021 (M-D-Y).
> Integrated graphics device with 4 adapter port(s)
- Secondary monitor is laptop’s integrated screen or built-in port
- Secondary monitor attached to adapter port #1
DirectX Settings
Safe mode: Off
OpenBLAS: OpenBLAS 0.3.30 DYNAMIC_ARCH NO_AFFINITY SkylakeX MAX_THREADS=64.
Rhino plugins that do not ship with Rhino
C:\Users\StefanoMenci\AppData\Roaming\McNeel\Rhinoceros\packages\9.0\BlockEditNew\2.1.7\blockeditnew.rhp “BlockEditNew” 2.0.0.0
C:\Users\StefanoMenci\AppData\Roaming\McNeel\Rhinoceros\packages\9.0\IntelliClad\0.0.11-beta\IntelliClad.TestInput.rhp “IntelliClad.TestInput” 1.0.0.0
C:\Users\StefanoMenci\AppData\Roaming\McNeel\Rhinoceros\packages\9.0\Rhino-MCP-Platform\0.2.1-wip\net8.0\RhinoMcpPlatform.rhp “RhinoMcpPlatform” 0.2.1.0
C:\Users\StefanoMenci\AppData\Roaming\McNeel\Rhinoceros\packages\9.0\CommandHistoryMD\0.1.0\CommandHistoryMD.rhp “CommandHistoryMD” 0.1.0.0
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 9 WIP\Plug-ins\Commands.rhp “Commands” 9.0.26209.18303
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 9 WIP\Plug-ins\3dxRhino.9.rhp “3DxRhino.9”
C:\Program Files\Rhino 9 WIP\Plug-ins\UpdatesAndStatistics\UpdatesAndStatistics.rhp “UpdatesAndStatistics” 9.0.26209.18303
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 9.0.26209.18303
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 9.0.26209.18303
C:\Program Files\Rhino 9 WIP\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 9 WIP\Plug-ins\MeshCommands.rhp “MeshCommands” 9.0.26209.18303
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoCycles.rhp “RhinoCycles” 9.0.26209.18303
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoCode\RhinoCodePlugin.rhp “RhinoCodePlugin” 9.0.26209.18303
C:\Program Files\Rhino 9 WIP\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 9 WIP\Plug-ins\SectionTools.rhp “SectionTools”
Here is how to reproduce it:
- Open the file in ScriptEditor breakpoint_test.py (21.6 KB)
- Set a breakpoint, for example, at line 332.
- Click
Debug active script to start debugging → Execution stops at the breakpoint, and both the call stack and variables panels look correct.
- Click
Continue debugging (the same button, with a different tooltip) → The code advances to the next loop iteration and stops at the same line, but the call stack now contains the unexpected doc(self) item.
- Click
Continue debugging once more → The call stack now contains two doc(self) sections.
The steps above reproduce the problem when using either the toolbar buttons or the corresponding options in the Run menu. However, the behavior is different when invoking the same commands with keyboard shortcuts.
While writing this reply, I tried using the keyboard shortcuts instead of the buttons, but kept encountering another problem.
If I start by pressing Shift+F5, execution begins and appears to stop somewhere. I cannot tell whether it has stopped at the breakpoint because the editor does not highlight the line. If I then press F5, the UI sometimes becomes unresponsive. The only way I have found to revive Rhino is to minimize ScriptEditor using its Windows taskbar button, then click the button again to restore it. The UI becomes responsive again, and I can stop execution.
It usually freezes after pressing Shift+F5 followed by F5, although it sometimes freezes immediately after the first Shift+F5 or only after pressing F5 several times. Both the ScriptEditor and Rhino windows become unresponsive. After minimizing and restoring ScriptEditor, I see a burst of output in Rhino’s command window, apparently caused by all the pending keystrokes entered while the UI was frozen.
