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.
So, I am running latest stable Xamarin Studio 5.8.1 Build 8 on MacOS 10.10.2...
I am creating a Xamarin Forms PCL Project and working in the PCL library.
It seems after 10-15 minutes or so, when I am typing and an auto complete would pop up, XS locks up. The beach ball of doom shows up and the Activity Monitor reports XS as having stopped responding... If I wait sometimes upwards of a minute, XS will come back and start responding...
I have noticed that the longer I run the more often the issue occurs and also it appears the code competition cache gets stale and stops updating and I am seeing method names and signatures on objects that have been renamed or changed.
So far in about 30 minutes or so of testing with Code Completion turned off... I am not seeing any more freezing.
Feel free to contact me for more info or however I can help.
It would be very useful if you could try something for me. If XS hangs again please do the following:
1) In the Activity Monitor, see what's the PID of the Xamarin Studio process.
2) Open a terminal a run the following command: "kill -QUIT pid" where 'pid' is the PID you found.
3) Attach the latest Ide.*.log file you'll find in ~/Library/Logs/XamarinStudio-5.0
Ok so here's the weird thing... I had previously turned off the Code Completion option... I've since turned it back on, and restarted XS and I haven't had any hang ups longer than a few seconds.
I have no idea how that could be... but it's been great after it was toggled back off and on.
I'll keep you posted.
Ok it's happening again... here's the log... The kill command wouldn't work, so I did a force quit from Activity Monitor...
Here are the ide logs...
Seeing lots of these in all of the logs too... every time I get the beachball...
Some times it comes back some times it doesn't...
Hoping you can gleam something useful from these logs or at least give me a work around... Really don't want to have to use VS and was one of my Xamarin machine activations.
Doh... forgot to paste:
"Warning slow edit action update."
In the last update...
I really need you to run the "kill -QUIT pid" command. This will not stop Xamarin Studio, this sends a special signal that the Mono runtime will interpret as a request to dump all stack traces. Those stack traces are dumped in the log file.
Added a new attachment with executing the kill command...
I'd like to say that log represents the SAME issue... I forgot to force quit Xamarin and after about 10 minutes... it started responding again like nothing happened...
Very weird and very frustrating...
Do you use F# in your projects?
Nope, not at all.
I haven't changed any options.. so everything should be "out of the box" installed... Just working on a Xamarin Forms PCL Based App using C# and Xaml.
This particular instance of the problem has been fixed in XS 5.9. As a workaround, you can try disabling the F# add-in. To do it, click on Add-in Manager in the Xamarin Studio application menu, then in the Language Bindings section select the F# binding and click on Disable.
The stack trace is showing a hang in the fsharp add-in that may still happen when editing f# files, so this needs further research. Reassigning.
You mean the sharp could still hang when editing c# files?
Ok thanks, I'll try disabling f# add-in and see if that takes care of my issues!
I have attached a log file produced with a "kill -QUIT PID" when Xamarin Studio hangs.
On my Mac, Xamarin Studio hangs every 10th minute.
@Dave The log in comment 10 does.
Pretty sure this has been fixed at some point. Most of the F# types and function calls that appear in the log don't even exist any more.
It isn't something that I've seen in the time I've been working for Xamarin.
Feel free to reopen if this bug still affects you.