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.
One of our customers reported encountering a Visual C++ Runtime Error, though they're unable to reproduce.
The Computer was locked. Signed on. And XS crashed.
Version 5.2.1 (build 1)
Installation UUID: 18a85229-8322-4775-b894-e5434e343804
Microsoft .NET 4.0.30319.18444
GTK+ 2.24.22 (MS-Windows theme)
Version: 4.14.0 (Enterprise Edition)
Android SDK: D:\DEV\SDK\Andriod\adt-bundle-windows-x86-20140321\sdk
Supported Android versions:
2.1 (API level 7)
2.2 (API level 8)
2.3 (API level 10)
3.1 (API level 12)
4.0 (API level 14)
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)
Java SDK: C:\Program Files (x86)\Java\jdk1.6.0_39
java version "1.6.0_39"
Java(TM) SE Runtime Environment (build 1.6.0_39-b04)
Java HotSpot(TM) Client VM (build 20.14-b01, mixed mode, sharing)
Release ID: 502010001
Git revision: d06832ce9807d6be24aca225457e8b37c7669f6f
Build date: 2014-08-07 14:35:09-04
Xamarin addins: 1de032531be4cecf2f39dbee3b87aac78204058c
Windows 6.1.7601.65536 (64-bit)
Need a trace or repro instructions to be able to do anything about this.
Created attachment 7701 [details]
Log files from error
Looks like a crash in libglib.
At the time of filing this bug report I did remember to ask the customer for followup info, but I did not remember to close out this bug when they were unable to do so. So doing that now.