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.