Hello VRChat team,

As a long-time user, I would like to share a positive observation regarding the recent improvements in client[1853] stability, specifically concerning how the engine handles Udon exceptions.

I recently observed a scenario in where a Udon script encountered a and became . While occur in various worlds, the client's behavior in this instance was particularly notable. While in the past such errors would often lead to instance-wide issues or a full client hang, I noticed that the engine now correctly isolates this exception.

Despite the script failure, the client maintained stability, allowing me to continue essential tasks such as navigating the world and exiting via portals without any interruptions. Although there was a brief latency (client freezing) during the process, it is clear that the client's current error-handling mechanism successfully isolated the failing script and prevented the entire instance from crashing.

I have attached logs capturing this event. I am sharing this because it demonstrates that the client's current error isolation and resilience mechanisms are working exactly as intended, providing a robust user experience even when world-specific scripts fail. I appreciate the hard work put into these underlying improvements and hope this log data helps you further refine the client's error-handling capabilities, particularly regarding the latency during the recovery process.

Best regards,

Riria Nee-chan

---

I have attached the full log for the session. The 'Udon Halted' event occurred around during my session in . You can check the logs around that time to see the engine's recovery process and the subsequent latency.