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
colinday
Feb 07, 2014 00:32
Still occurring on Unity 4.3.4f1
iMac
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
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.
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.
sdvoynikov
Feb 06, 2014 04:07
Unity 4.3.4 Bug still here (mac mini mid 2011, macbook pro 15" retina early 2013)
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.
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.
SO FRUSTRATING!
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
donut2d
Jan 31, 2014 18:20
Still experiencing this on Unity 4.3.4f1.
JKyy
Jan 30, 2014 13:42
I would really like to see this issue been fixed. It is very frustrating. Even an info whether the issue is reproducible on Unity Tech's end would be good news. If more info is needed for reproduction, I am sure many us will help. Here is a sampling ( http://pastebin.com/n6De5kJq ) on my Mac done from the Activity Monitor once I have attached to Unity Editor process from the Monodevelop and clicked "Play" in Unity Editor. Unity application is now stuck in non-responding state.
iKonrad
Jan 30, 2014 11:31
Thing that is depressing me the most is that we still did not get any official statement from Unity Team.
Come on, debugging is a crucial part of serious programming - it is a priority 1 since it breaks the regular development workflow! Do something guys.