Search Issue Tracker
Fixed in 4.5.X
Votes
225
Found in
4.3.0f2
Issue ID
573949
Regression
No
Stepping out while debugging causes the standalone player to freeze
To reproduce:
1. Build Angry bots x64 standalone on OSX 10.9
2. Put a breakpoint in FreeMovementMotor line 18
3. Pin some variables
4. Attach to player
5. Hit breakpoint, step through some code
5. Player crashes (stack trace attached)
Expected result: Debugging proceeds
Actual result: player freezes
*Note :
The issue is related to Stepping Out when debugging and is fixed. We found another issue related to Stepping Over which has the same result, the player freezing but it only occurs when using Step Over.
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
shloob
Jan 30, 2014 02:23
@Unity Devs - This issue is not specific to the repro steps above, it happens with every single one of my projects. Attach MonoDevelop to Unity Run and Debug hit a breakpoint. Stop running and try to run again and Unity becomes unresponsive. Then you must force quit unity, quit monodevelop, then open unity, then open monodevelop. Rinse and repeat, the same every time.
shloob
Jan 30, 2014 02:17
Yes please vote for this issue. This makes using Unity extremely frustrating, I can't believe that this is ranked as a Priority 3 issue. It has been happening for several versions, and did not get any better with version Unity 4.3.3f1. Someone please fix this!!!!
Zincoontrin
Jan 29, 2014 21:18
SETHK: I'll open a kickstarter campaign for you :)
sethk
Jan 28, 2014 22:22
MonoDevelop is open source, so possibly a workaround/fix exists there. Who will donate me some money if I can solve the issue? (half-joking)
FredDeschenes
Jan 28, 2014 19:44
Unity 4.3.x
OSX 10.7.5 (Lion)
Same issue, cannot but breakpoint (never had any issues with Unity 4.2).
As IQPierce mentionned, this is a super critical bug. I do not get how the IDE integration can be SO broken (cannot debug, can't even open the correct project most of the time when working on multiple projects at once, etc) on OSX and Windows and this not being a top priority bug. This is turning professional developers away from Unity...
vito-c
Jan 27, 2014 19:38
OSX 10.8.5
Unity 4.3.3f1
Unity is freezing after running the debugger about 75% of the time. Usually works the first time I run it then if I leave the debugger attached and run the game again unity will freeze
TomD3
Jan 22, 2014 20:50
Same here; totally useless on the Mac (Maverick with Unity 4.3.3f1); sometimes it works, sometimes it doesn't. It's not a small problem, it's a showstopper for many people.
Do we have any kind of workaround?
sdvoynikov
Jan 22, 2014 01:18
Have this issue for a long time: when monodevelop connected to editor, editor will freeze when trying to launch play mode. Actual for several versions of Unity, since about 4.2 until current 4.3.3
donut2d
Jan 22, 2014 00:34
I'm experiencing this on OS X 10.9.1 and Unity 4.3.3f1. I really hope this is fixed soon. It's discouraging to see that this has been happening since November 20th, two months ago.
Zincoontrin
Jan 14, 2014 23:17
More than 1 month has passed and no solution in 4.3.3 to this yet :(