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.

Comments (84)

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

  2. Zincoontrin

    Jan 14, 2014 23:17

    More than 1 month has passed and no solution in 4.3.3 to this yet :(

  3. broepstorff

    Jan 13, 2014 20:25

    I was just able to repro this on 4.3.3 on my machine. Still a blocking issue!

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

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

  6. 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).

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

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

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

  10. iKonrad

    Dec 11, 2013 01:21

    Have the same issue. I just can't believe how they can release software that bugged.

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.