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.
In the course of working with Xamarin Android axil files, often I will double click one in the solutions pane and XS will stick, showing "Opening xxxxxxxxxxx.axml". The only way to get out of it is to restart XS. Right now I am doing some work that requires a single line alteration on about 30 different axml files and I have had this happen 9-10 times in the last 20 minutes. I have also had this bug happen on multiple Macs, with (obviously) separate installs of XS.
I also get a bug that will prevent an edited axml from saving changes. So I will do a bunch of work on one, save it, close the tab out, and then open it again only to find that all the changes were not saved. I am to the point now that I have to select all, copy, close the file, open it, select all, paste and then save again, just to get my edits to save.
What logs would be useful to help fix this?
You can attach the logs you find in the directory opened by doing Help -> Open Log Directory in Xamarin Studio. That should give us a good start in figuring out the issue. Can you also paste your version information from the "About Xamarin Studio" dialog (Show details -> Copy Information).
Which logs would you like? AndroidTools, Components, ide? I ask because I had so many crashes while experiencing this problem that Xamarin Studio created a lot of them, 30 in 1.5 hours, and bugzilla only lets me upload one at a time.
You can zip them all up in one archive to attach and I will dig through them.
Created attachment 19952 [details]
Xamarin Studio Logs
=== Xamarin Studio Enterprise ===
Version 6.1.5 (build 0)
Installation UUID: e727558c-1f19-4279-b2aa-a5a87b525240
Mono 4.6.2 (mono-4.6.0-branch/ac9e222) (64-bit)
GTK+ 2.24.23 (Raleigh theme)
Package version: 406020016
=== NuGet ===
=== Xamarin.Profiler ===
=== Xamarin.Android ===
Version: 188.8.131.52 (Visual Studio Enterprise)
Android SDK: /Users/****/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
6.0 (API level 23)
7.0 (API level 24)
SDK Tools Version: 25.2.5
SDK Platform Tools Version: 25.0.3
SDK Build Tools Version: 25.0.1
Java SDK: /usr
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
Android Designer EPL code available here:
=== Xamarin Android Player ===
=== Apple Developer Tools ===
Xcode 8.2.1 (11766.1)
=== Xamarin.iOS ===
Version: 10.3.1.8 (Visual Studio Enterprise)
Build date: 2016-12-20 02:58:14-0500
=== Xamarin.Mac ===
Version: 184.108.40.206 (Visual Studio Enterprise)
=== Xamarin Inspector ===
Build date: 2/16/2017 10:57:39 AM
=== Build Information ===
Release ID: 601050000
Git revision: 7494718e127af9eaec45a3bd6282d3da927488bd
Build date: 2017-01-17 10:31:01-05
Xamarin addins: c92d0626d347aaa02839689eaac2961d24c9f446
Build lane: monodevelop-lion-cycle8
=== Operating System ===
Mac OS X 10.12.3
Darwin Sevrens-MBP.wavecable.com 16.4.0 Darwin Kernel Version 16.4.0
Thu Dec 22 22:53:21 PST 2016
=== Enabled user installed addins ===
Xamarin Inspector 220.127.116.11
From what I can see in the logs, it looks like your layouts are using the appcompat support library from Google. If so you should have a Material family theme or your own derived theme setup in Android Manifest ("Application theme" entry) or alternatively select it in the designer theme dropdown. Your layout should render after that.
Can you confirm it does? Thanks
So we are using a custom theme with Theme.AppCompat.Light.DarkActionBar as the parent theme. The layout renders just fine. It is just that sometimes (4 out of 5 times) opening one of them will cause the ide to stop responding. The editor is set to default so I will set it to the custom theme and take some time to mess with it and see if it makes a difference.
Ok, so I was able to confirm that having the theme set in the editor makes no difference. I am still getting the freeze up. And while having the theme selected in the editor, it will randomly get set back to default while I am working on the file. And this time when it froze up, I knew it was about to happen because I kept making changes to the file in the Designer and they would not get applied (change the margin or color of something and the change would not show). Once I noticed this, I close the file and tried to reopen it and then I got the freeze. Logs are uploaded.
Created attachment 20017 [details]
Xamarin Studio Logs 2
Hello, what is the current status of this bug? I am continuing to get this even on the latest stable builds. I cannot go a day without having to restart Xamarin Studio multiple times because it freezes up when trying to open an AXML in the editor. This is getting VERY frustrating.
Once you detect that Xamarin Studio is getting frozen could you open a terminal and issue the following commands:
$ ps ax | grep Xamarin Studio
[Process ID] /Applications/Xamarin Studio.app/...
$ kill -QUIT [Process ID]
And then attach your Ide.log file again. It should now contains a global stacktrace of all the threads of the IDE.
Also to confirm, this freeze you are experiencing doesn't happen for other parts of the IDE (as in you can switch file tabs, click menus and so on)?
Thanks so much for taking the time to submit this report! I suspect that this is a duplicate/related to issue 42037, which is very reproducible.
*** This bug has been marked as a duplicate of bug 42037 ***