I needed this patch for a fix but now I can’t debug anymore.
I have VS tool 2.1.0.0
Anyone have a workaround?
I needed this patch for a fix but now I can’t debug anymore.
I have VS tool 2.1.0.0
Anyone have a workaround?
Play + Attach in VS: Work
Attach in VS + Play: Doesn’t work anymore
Having the same problem in 5.2.1p2
Also noticed the ‘Select Default Editor’ appears to be missing from Project Settings so I can’t set my scripts to open in Mono either.
I also have this problem. I submitted several bug reports with crash dumps (736495, 736117, 736035, 736026, 736021, 736015, 736011, 736000, 735792). Perhaps a tad overkill but I was told submitting the dumps is always a good idea.
Tried 5.2.1p4, 5.2.1p2 and 5.3.0b2.
Hi, thanks for reporting this issue.
We currently investigating it.
A work-around for this issue is to use VSTU 2.0. We are still looking into this issue and will report back with an update once we found the root cause.
@lukaszunity here the issue is with VSTU 2.1 (the latest downloaded here)
The root cause of the issue has been found and fixed. Will update again once I know which release this fix will land in.
Will be fixed in Unity 5.2.2
thanks, and is far from the release? (just to valutate to wait or to rollback to the previous patch) ![]()
The release process for it has been started, should be released this week unless there are some ship stoppers.
great news!
Great news, was about to post the same issue.
Same problem for me, good to hear that it will be fixed soon ![]()
Till it is not released: Have anyone a download link to VSTU 2.0?
You cannot download VSTU 2.0 from the official website, only the latest version. I do not recommend downloading it from other places.
I’m afraid the issue is still present in Unity 5.2.2f1. I’ve uploaded a new crash dump (738250).
Does this also happen for you on a new single script project? And do you know if you have this issue in MonoDevelop? The debugger clients in Visual Studio and MonoDevelop are different and therefore do not behave in the same way.
The call-stack from your log is different than the issue that was fixed. Your call-stack seems to indicate that the debugger in Unity crashes when trying to retrieve the stack frames for a thread and it looks like a real and different bug. In order for us to be able to fix this issue you need to send in a project in which we can reproduce the crash.
I’ve created a new bug report and attached a project which triggers the crash (fresh project, single script) a couple of hours ago. I’ve yet to receive the ID to give you for some reason, usually this happens within minutes. I’ll post it once the bug report has been processed.
Fixed my issue, thanks.
Issue ID is 738481. Thanks!