Constant crash on breakpoint in 4.1.3

Unity Engine
1

Since going to 4.1.3 I’m getting the following problem when I hit a breakpoint in MonoDevelop:

Unity Bails, showing the ‘report error’ page and MonoDevelop show a window saying:

The Debugger is waiting for an expression evaluation to finish.
Method: System.Collections.Generic.List’ 1[[System.String, mscorlib, Version=2.0.0.0,Culture=neutral,PublicKeyToken=b77a5c561934e089]].get_Count

Anyone know what’s happening ?

2

Getting this on game launch now… Same ‘The Debugger is waiting for an expression evaluation to finish’ but with a different second line. Going back to 4.1.2 to double check it’s a new version problem.

3

Same breakpoints working fine in 4.1.2

It’s a 4.1.3 problem 8(.

4

Seeing the same here.

  • Upgraded to Unity 4.1.3 (OS X, 10.8.3)
  • Attached MonoDevelop to a VERY simple scene (though mind you, I’m testing a new framework)
  • Unity reported a null pointer
  • Set a breakpoint
  • Unity crashed when it hit the breakpoint.
  • Happened repeatedly.
5

Hadn’t restarted my Mac since installing. Doing so seems to have cleared up the crash.

HTH, mslinklater

6

Oops. I spoke too soon. Problem’s come back. :stuck_out_tongue:

7

I tried a full power down and reboot of my Mac… didn’t make a difference, still crashed. Dropping back to 4.1.2 worked.

8

Am having the same issue with 4.1.3f3.

Is Unity going to release an update / fix for this? Or is there any other workaround (other than switching back to 4.1.2)?

9

Same issue here, both problems listed above. Good news on 4.1.3 is our skinned animations are running fast again but no debugging sucks. Have to roll back or revert to good ol’ console logging. Hopefully addressed soon.

What I have been doing is release builds in 4.1.3 and then debugging in 4.1.2 for now. I typically keep each Unity version back 2-3 versions and still have a 3.5.7 as well to help issues like this. Debugging works great in 4.1.2, lots of great fixes in 4.1.3 though but some regression it seems on debugging. Framerate for our shooter is 20-30% better in 4.1.3, 4.1.2 had some regression on skinned animation speeds. Looking forward to an update soon to fix this. Maybe it is just related to Mac editor as I haven’t tried on Windows.

Unity Version 4.1.3r3
OS: OSX 10.8.3

10

I’m facing this issue too with 4.1.3f3. - very annoying

11

I just started getting this today. Any suggestions?

Edit: Sorry, I posted here before finding the following thread, which seems to better narrow down the problem to compatibility with Mavericks.

http://forum.unity3d.com/threads/183516-4-1-3-crash-when-hitting-monodevelop-breakpoint-on-OSX

12

Unfortunately, this is a constant problem with all Unity versions I’ve tried and not specific to the OS. I have the same problem on Windows 7. But it’s just worse on Mavericks (never tried with previous OS X versions).

Attach MonoDevelop to Unity, Press Play, Hit a breakpoint and try to inspect any variables and you’ve got a nice crash.

So please Unity guys, fix this !

13

I am experiencing this issue in Unity 4.5.0f6 and Mono 4.0.1

Has a solution been found for this?

I’d also like to mention, I was using this version for at least a month with no problems until last couple of days. I am trying to debug loading a XML document and when I try to look at the data when a breakpoint is hit, the debugger message appears twice before timing out.