Search Issue Tracker

Fixed in 4.5.X



Found in


Issue ID




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.

Comments (84)

  1. davekalina

    Feb 18, 2014 20:11

    It's fairly ridiculous that debugging is currently broken in a major release. Debugging in MonoDevelop is a CORE PART of my job as engineer, and I'm constantly running into roadblocks.

    My debug workflow was just fine with Unity 4.2, we had to upgrade for other features, and now I can't debug past a single session (I can attach to process and hit play and debug once... and then a subsequent attempt at running the game will result in Unity and MonoDevelop locking, and I have to use Activity Monitor to kill both processes before starting again).

    Please address this!

  2. blernsball

    Feb 16, 2014 21:46

    Broken for me. OSX 10.9.1, Unity 4.3.4.f1

    Sometimes it works, sometimes it hangs Unity, sometimes it won't attach...

    To be honest, considering how well thought out other features are, I'm surprised at how poor debugging is in Unity.

  3. colinday

    Feb 07, 2014 00:32

    Still occurring on Unity 4.3.4f1

    OSX 10.9.1 (13B42)
    27-inch, Late 2009
    Processor: 2.8 GHz Intel Core i7
    Memory 16GB 1067 MHz DDR3
    Graphics: ATI Radeon HD 4850 512 MB

  4. It3ration

    Feb 06, 2014 19:28

    I am able to debug if I attach -after- hitting play in Unity. You can also debug Awake() functions if you hit pause, then attach, then hit play (disgusting I know). Let's hope someone is paying attention over at Unity because this is really ridiculous.

  5. It3ration

    Feb 06, 2014 19:12

    This is still an issue. We are a major studio, the Unity devs need to be more transparent with their developers.

  6. sdvoynikov

    Feb 06, 2014 04:07

    Unity 4.3.4 Bug still here (mac mini mid 2011, macbook pro 15" retina early 2013)

  7. TomD3

    Feb 05, 2014 22:42

    This is still happening with the latest version (4.3.4f1). Impossible to debug on OSX Maverick.
    It is a huge problem as you basically can't work with Unity on a Mac anymore.

  8. aureliocalegari

    Feb 03, 2014 05:52

    4.3.4f1 works intermittently. More likely to hang. The way it's more likely to work is to:
    1) Start Unity;
    2) Start monodev;
    3) Hit the game 'play button' (before attaching the debugger);
    4) From mono, attach the debugger.
    5) Detach the debugger;
    6) Stop the game.

    Anything other flow that does not follow the above will hang Unity or sometimes even Unity & Mono.


  9. broepstorff

    Feb 02, 2014 02:06

    Seems to have been fixed in 4.3.4 for me, at least. (OSX Mavericks + Macbook Pro 15" 2011). Am guessing this was related to the OpenGL driver workaround mentioned in the release notes

  10. donut2d

    Jan 31, 2014 18:20

    Still experiencing this on Unity 4.3.4f1.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.