Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
4.3.4f1
Issue ID
612251
Regression
No
ManualResetEvent fails if the mono debugger is attached
To reproduce:
1. Create a script:
using System.Threading;
using UnityEngine;
public class Test : MonoBehaviour
{
private ManualResetEvent m_ResetEvent;
void Start()
{
m_ResetEvent = new ManualResetEvent(false);
var thread = new Thread(WaitPlease);
thread.Start();
}
private void WaitPlease()
{
m_ResetEvent.WaitOne();
Debug.Log("How could I possibly be here?");
}
}
2. Attach the script to the camera
3. Enter/leave play mode - console is clean
4. Attach monodevelop debugger to Unity
5. Enter/leave play mode - notice that the console now has "How could I possibly be here?" - the ManualResetEvent did not work
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
CharlesWoodhill1
Aug 22, 2014 17:50
seems the debugger autosets all wait handles... (EventWaitHandle, Mutex, Sleep)
Synastry
Jul 28, 2014 04:40
This bug is also reproducible by calling IAsyncResult.AsyncWaitHandle.WaitOne method with an IAsyncResult instance returned by async I/O method like TcpClient.BeginConnect.
This bug let programmer cannot use connecting with timeout functionality while debugger is attached.
I really hope this issue to be released in near future release.