benaclejames / benaclejames/VRCFaceTracking
Rare UI freeze upon socket conflict.
- Dominant language
- C#
- Stars
- 907
- Forks
- 135
- Avg merge
- 11h 28m
- Merged PRs (30d)
- 7
Description
Noticed when (in very rare instances) where the IP endpoint fails to bind (socket conflict), it will freeze the UI.
https://github.com/benaclejames/VRCFaceTracking/blob/25f7e9548505978be648e8ecf3a507afc14103c3/VRCFaceTracking.Core/Services/OscRecvService.cs#L60-L85
The try/catch can fails and return null, presumably causing the issue. Haven't investigated it deeply yet but it seems like the problem originates here.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at VRCFaceTracking.Core/Services/OscRecvService.cs, lines 60-85, and inspect how a failed socket bind and the try/catch return value are handled. Reproduce a socket conflict if possible, then verify that the UI remains responsive and the failure is handled without causing a null-related freeze.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100