Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
This happens especially right after you opened it. Sometimes you actually have to force close.
Frequency: 1 out of 10. Lately more often
We have tried to reproduce this issue. But not able to reproduce.
XS 4.2.2(build 2)
My project where it happens mostly has some web references.
Can you please get a kill -QUIT trace of the hung process?
To do so, run "killall -QUIT XamarinStudio" in a terminal while XS is hung. This will cause it to write a backtrace fo all threads to its log file. Then find the log file using Help -> Open Log Directory and attach it to this bug.
Haven't experienced it lately as I finally was able to mostly use VS. However since VS doesn't support many things yet, I'll go back to XS and let you know the next time it happens.
However, couldn't it be related to this:
Any logs we can use? :D
Seems to be same issue as bug 13181?
Fixed in more recent versions.
As per Comment 4 User is not getting this issue anymore. As of now I am closing this issue.
@Andy: Please feel free to Reopen it, if you are getting this issue again.