Copyright © 2026 Unity Technologies
Thank you for reporting a bug to Unity. We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available. Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
In very rare, obscure UI scenarios, a "Handles.Repaint called outside an editor OnGUI" is sometimes logged.
Steps to reproduce:
Actual results: "Handles.Repaint called outside an editor OnGUI" error is thrown
Expected results: No errors are thrown
Reproducible with versions: 6000.3.0a3, 6000.3.9f1, 6000.4.0b9, 6000.5.0a7
Not reproducible with versions: 6000.0.67f1, 6000.3.0a2
Tested on (OS): MacOS Silicon Tahoe 26.2
Note: The issue is inconsistent
UPDATE: This error is harmless.
It's intended to warn the user they're attempting to repaint a SceneView Handle outside of OnGUI(), which isn't allowed. However, in this scenario it's being triggered by a race-condition caused by a modal Dialog Box shown by an AuxWindow that's opened by a SceneView Overlay. In this case, the Repaint call is unnecessary and is simply ignored (but the error is still logged).
It doesn't occur on Windows because the platform timing of the modal UI is different than macOS resulting in different code paths being executed which sidesteps this scenario.
Issues you vote on will appear here