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

Mono

-

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.

Log in to vote on this issue

Comments (82)

  1. SigKST

    Mar 25, 2014 19:52

    No amount of workarounds makes this ok to leave unresolved. Still seeing this and variations of this in 4.3.4f1.

  2. disturbing

    Mar 20, 2014 21:26

    This is still an issue =/ So annoying!

  3. Troyminator

    Mar 11, 2014 15:29

    Still seeing this in 4.3.4. Additionally, I'm seeing the following, which I believe is related:

    - Start Unity game by hitting play.
    - Set a breakpoint and attach the debugger to the Unity process.
    - Make sure the code hits that breakpoint.
    - Hit 'Go' in the debugger.
    - Detach the debugger.
    - Quit MonoDevelop.
    - MonoDevelop freezes without actually quitting. Force Quit required to close the process

    Running Mac OS X 10.8.5
    27-inch iMac, Late 2012 Model
    3.4 GHz Core i7
    8 GB 1600MHz DDR3 RAM
    Unity 4.3.4f1
    MonoDevelop 4.0.1

    Hope this helps.

  4. AquaGhost

    Feb 26, 2014 19:42

    Still getting this on 4.3.4 late 2013 macbook pro retina 15.

  5. Cybexx

    Feb 26, 2014 01:22

    4.3.4f1 with Mavericks is debuggable but only if the debugger isn't attached while the script is compiling. If Unity goes into script compilation with the debugger I am getting 100% crash rate around multiple projects and multiple machines.

    If you attach the debugger after play mode is running then I never get a crash but if after that I stop Play mode and hit Play again it will crash if that causes the compiler to trigger.

  6. Stephan_v

    Feb 20, 2014 18:37

    @RELAYONE those are how many votes you have personally left to devote to issues. There is no vote threshold for bugs in that manner.

  7. relayOne

    Feb 19, 2014 15:07

    Why is the "votes left" frozen at "9"? I've seen votes increase from 50 to 124, and the entire time the "votes left" has been locked on 9. I'm getting the impression that this issue is not important to Unity, and it doesn't matter how many votes this issue is getting.

  8. davekalina

    Feb 18, 2014 20:32

    Worth noting that I am running MacOS 10.8.5, Unity 4.3.4f1, and MonoDevelop 4.0.1

  9. 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!

  10. 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.

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.

Latest issues

See all new issues