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
Comments (2)
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
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
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.