Bug 28313 - Getting XS Crashed on creating C# android project.
Summary: Getting XS Crashed on creating C# android project.
Status: RESOLVED DUPLICATE of bug 28323
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: unspecified
Hardware: PC Windows
: High major
Target Milestone: master
Assignee: Greg Munn
URL:
Depends on:
Blocks:
 
Reported: 2015-03-23 02:11 UTC by Arpit Jha
Modified: 2015-03-25 05:33 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED DUPLICATE of bug 28323

Description Arpit Jha 2015-03-23 02:11:55 UTC
Getting XS Crashed on creating C# android project.

Actual Result: While creating C# android application I have observed that XS got crashed couple of times. This issue also encountered on more than 1 machines.
However this is an intermittent  issue and not consistently occurs.

Environments having one or more instances of this issue:
Windows 8.1 (64 bit)
Windows 7(64 bit)
Windows 8(64 bit)

Expected Result: Application should create and deploy successfully.

Regression Status: This issue does not exist with  XS 6.0.0.69.

Screencast: 
http://www.screencast.com/t/tjruytVb8nP

Supplement Info:
Ide Log: https://gist.github.com/Arpit360/a2c2542ae18347b1ee03

Environment Info:
[Master Build]
=== Xamarin Studio ===

Version 6.0 (build 224)
Installation UUID: a0cab582-25eb-47fe-aa4a-c41ae667ad31
Runtime:
	Microsoft .NET 4.0.30319.34003
	GTK+ 2.24.22 (MS-Windows theme)
	GTK# 2.12.26

=== Xamarin.Android ===

Version: 5.1.99 (Trial Edition)
Android SDK: D:\android-sdk
	Supported Android versions:
		2.3    (API level 10)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
Java SDK: C:\Program Files\Java\jdk1.7.0_67
java version "1.7.0_67"
Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

=== Xamarin Android Player ===

Version: 0.2.5
Location: C:\Program Files\Xamarin Android Player\DeviceManager.exe

=== Build Information ===

Release ID: 600000224
Git revision: 13b6d6fc748c33d1c33c366755d3a053998454f1
Build date: 2015-03-22 10:08:29-04
Xamarin addins: b6bdd41ea6dbff307345f11c28bf15915dcb8558
Build lane: monodevelop-windows-master

=== Operating System ===

Windows 6.2.9200.0 (64-bit)
Comment 1 Greg Munn 2015-03-23 12:55:16 UTC
I've created about 12 projects in a row and not experienced the crash. If you could add anymore information to try and narrow it down that would be good. 

I don't know if the last few crashes in the log had anything to do with XS crashing or not, but they don't appear to be related to the android add-in.
Comment 2 Matt Ward 2015-03-25 05:31:35 UTC
This is fixed in 6.0.0.227 on master. There was a problem under Windows where the the Process.ErrorDataReceived event would sometimes have a null Data property on Windows.

https://github.com/mono/monodevelop/commit/762bf0a2be6d8cc18a166294dde1eec347b46fdf
Comment 3 Matt Ward 2015-03-25 05:33:01 UTC
This fix has also been applied to the 5.9 branch.

Marking as duplicate.

*** This bug has been marked as a duplicate of bug 28323 ***