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
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
- [macOS] Display flickers with bright colors when built Player uses 2 or more Displays
broepstorff
Jan 13, 2014 20:25
I was just able to repro this on 4.3.3 on my machine. Still a blocking issue!
relayOne
Jan 08, 2014 16:25
I'm noticing that not everyone who has posted comments to this topic is voting for the feature. Please make sure to vote for it by clicking on the vote button.
Thormor
Jan 07, 2014 20:45
This issue still happens with 4.3.2. Please fix ASAP. I had to update from Unity 4.2 since debugging with Maverick was impossible. Now an issue relative with debugging.
relayOne
Jan 05, 2014 16:32
I'm seeing this bug consistently. I'm running Mavericks 10.9.1 and Unity 4.3.1f1. I agree this bug should be priority 1. I'm resorting to Debug.Log statements for all debugging (welcome back 1990).
IQpierce
Dec 30, 2013 19:51
This is a critical workflow limitation for any serious developer trying to work in Unity on Mac. If Unity didn't have the capability to debug in the editor, no serious developer should try using it as a game engine, period. This has been broken for months.
How is this priority 3?
I'm seeing this bug 100% of the time when I try to attach debugger to the editor. Here's my system specifics; note that I'm on a pre-Mavericks OS X:
- OS X Version 10.8.5
- Mid-2010 Macbook Pro model
- Unity version 4.3.2f1
- MonoDevelop-Unity version 4.0.1
wintermute
Dec 20, 2013 02:49
I've been able to Debug before in Unity 4.2.x (before native 2D tools and mono upgrade were introduced). Now it just hangs endlessly.
OSX 10.9.1
MBP Mid-2012
Please fix, it's been here for a while now.
Tiktaalik
Dec 17, 2013 00:03
I've never been able to debug on OS X. It simply hangs endlessly when I try to attach to Unity. Has happened prior to Mavericks, on Mavericks, 4.2, and 4.3.
iKonrad
Dec 11, 2013 01:21
Have the same issue. I just can't believe how they can release software that bugged.
Wenceslao
Dec 08, 2013 09:19
On 4.3.1 on OS X Mavericks I can connect the debugger and even stop playing once. After that if I hit play again or try to compile scripts Unity locks up.
froodydude
Dec 06, 2013 10:37
I get this on OSX 10.7.5 with Unity 4.3 and Unity 4.3.1.