4.1.3 crash when hitting monodevelop breakpoint on OSX

Upgraded as prompted by the editor this morning. Every time I try to debug with monodevelop, unity freezes, prompts to send a bug report, and I have to kill it by hand. Anyone else get this? Tried deleting and reinstalling.

Had to roll back to 4.1.2 to be able to debug again.

Running OSX 10.8.3.

 

i am getting a similar thing happening on my macMini. I also have osx 10.8.3.. I can't even open Unity. Can we get some assistance please.

 

Reporting the same issue on multiple machines here. Error message references a "ToString" call. We've rolled back all OSX machines to 4.1.1

 

Was just about to update my 4.1.2 that I have now gotten to run quite stable on the Mac. Luckily checked the forum before I started. Think I gonna wait a few weeks....

Strange how they are able to do this sort of stuff with every release. Maybe a few Mac on the QC department would help ?

 

Just chiming in to say the same - 4.1.3 and crash as soon as I hit a breakpoint.

 

Me too ! In the v 4.1.3f3, editor crashes when hit the break point, and apart from this, the mono developer takes much more time to start.

I'm using OSX 10.7.5

 

Yup, same here (OSX 10.8.3). Submitted bug report...

 

Same here running OSX 10.8.3 with Unity 4.1.3. Submitted a bug report via the unity dialog.

 

Yup, same here!

Running OSX 10.8.3 with Unity 4.1.3 (worked fine in 4.1.0)

 

Same here, too, on MacOS 10.7.5. I reverted to 4.1.2 and the debugger works again.

 

Yep me too. Unity crashes when ever it hits a break point using mono develop. Worked fine in 4.1.2 but I cant use that because the profiler is totally borked with 10.8.3 and unity 4.1.2.

Leiv make sure that the git external is disabled within MonoDevelop. I found that to make MonoDevelop horribly slow.

SO yes Unity please fix this breakpoint monodevelop issue....

 

Yeah right ?! Every release seems to break things.

 

One more instance for me. same as everyone else here.

 

Ditto. 4.1.3 breakpoints are barfed.

 

My project won't even load without Unity crashing....

 

+1

 

Unity 4.1.3 on my 27'' iMac running Mountain Lion. I can hit a break point just fine and step through but anytime I inspect any member or variable, Unity instantly crashes. I'm going to try to roll back to 4.1.2.

 

Same here. On OSX 10.8.3, Unity 4.1.3 crashes instantly upon hitting any breakpoint.

 

Five days of bumping the thread? Well don't worry the devs are on it. (and have been on it for several days)

 

Well when a CORE feature of the engine is completely broken in a release, a forum discussion is confirmation to one another that it isn't something any one of us is doing wrong. I finally got an e-mail today saying that they are aware of the bug and have a fix but it won't be available until another release. That's unfortunate because several people here are on deadlines or have projects and when you don't hear a peep from a dev, the only thing you can do is share, file bugs and find a solution. Luckily I was able to roll back to 4.1.2 without too much damage.

 

Thanks for letting us know you're working on it, that is good news.
However people will keep bumping it until it is "noticed" - being able to debug is a pretty important thing.
There are quite a few bugs in my game that I simply can't fix until I am able to breakpoint debug again.

Hopefully it can be resolved soon and a quick update is possible.
Again though, thanks for letting us know you're working on it.

 

I'm getting the same, on OSX crashing every time a breakpoint is reached.

 

Thanks for giving official word, UnLogick.

 

Just for the record I'm having the same problem in Mountain Lion, trying to inspect a variable means a crash.

Does this work on older versions?

 

Same problem here. OS X 10.8.3 Unity 4.1.3f3

 

Is there any update on this?

 

This is constantly happening to me still... 4.1.5 may have fixed it, but it's broken again as of 4.2.1f4.

BAH... such an important thing to have working... frustrating.

 

Same here. Is there any word when this is getting fixed?

 

It's worth noting that I'm on Unity version 4.2.2 and I just upgraded my OS to Mavericks. How does this issue, which apparently existed in an earlier version and was fixed, pop up again? Mavericks has been available to test against for months. Reverting back to an older version of Unity is not possible in my case and I no longer have a script debugger.

 

Yeah I've noticed today that with 4.2.2f and OS X Mavericks I can't debug. Crashes every time I hit a break point.

On the plus side my mouse no longer stops working whenever I quit Unity.

 

Exact same problem here 4.2.2f and OS X Mavericks = Mono crash when hitting a breakpoint!

 

* BUMP *

4.2.2f1 and OSX Mavericks; Unity crash on debug breakpoint hit every time.

Having to revert to oldskool print().. not pleasant

 

I have the same problem. PLEASE fix this, it's a pretty critical feature for any dev.

 

Same here. Now I have Unity that doesn't work on Mac and Windows 8.1. Joy... Remind me why I paid for this again?

info:
Mavericks + Unity 4.2.2 and Unity 4.2.1

Bug Submitted (Case 571962).

 

Same here, crash on monodevelop breakpoint. Mavericks + Unity 4.2.1 and Unity 4.2.2

Bug submitted case 571747

 

Same here Unity 4.2.0 + Mavericks, crashes everytime i get to a breakpoint

 

Also a new Mavericks user encountering this issue.

 

Please refer to this thread : http://forum.unity3d.com/threads/203895-Unity-3D-4-2-with-OSX-Mavericks-GM/page5

Alright many people reporting this issue with Maverick. Sadly the only answer that we got is it will be fixed for 4.3.

 

Fixed for me in Unity 4.3.0.f4 running on OS X 10.9.

 

Still not fixed in 4.3...

Yes I worry and we probably need years of bumping at this rate...

 

I noticed that the latest version is 4.3.1. Does anyone know if 4.3.1 fixes this issue or have you already updated and tested? (I've got 4.3.0f4)

 

I can't seem to edit my post above, but just as a head's up, I downloaded 4.3.1 and now I can debug! So I recommend trying to get this latest version...

 

Doesn't work for me, I'm on unity 4.3.1f1, on Mountain Lion, and each time I try to debug, Unity beachballs me 'til death

 

Doesn't work for me either on Mavericks and 4.3.1f1. I try attach to process, start project in Unity3D, breakpoint is never reached and Unity is beachballing and stuck.

 

Resolved for me by enabling Script Debugging and Development Build in Build Settings.

 

Not resolved for me! :sad: Anyone else? @SudoVega: Have you got it working consistently?

 

Yes, it has worked ever since for me.

 

Hey!
There is a workaround to make it work.
I've gather all the info here https://gist.github.com/y-a-r-g/8554014

 

yarg that link is broken for me.