Search Issue Tracker
Not Reproducible
Votes
0
Found in
1.0.0-pre.20
Issue ID
UUM-132199
Regression
No
Editor randomly freezes on "TouchGestureResponder was not found in the responder chain during removal" and has to be shut down
How to reproduce:
1. Open the attached project "Hackweek2D"
2. Interact with the Editor for some time or leave it unfocused
3. Observe the results
Expected results: The Editor is responsive
Actual results: The Editor freezes at some point and has to be killed
Reproducible with: 1.0.0-pre.20, 1.5.0-pre.1 (6000.4.0b4)
Reproducible on: macOS Tahoe 26 (M1)
Not reproducible on: No other environment tested
Notes:
- The freeze is consistent but might occur more reliably and faster when interacting with the AI related tabs
- Freezes don't happen after deleting the AI packages
- Freeze sometimes happens with the Editor focused but most of the times it happens while it's unfocused
- Deleting the Library folder doesn't fix the issue
- It was previously attempted to manually delete the AI packages fromt the project
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.