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.
Version 4.2.2 (build 2)
Installation UUID: 7caad2c9-2363-4a81-9dee-4d0efe64b4ef
Mono 3.2.5 ((no/964e8f0)
GTK+ 2.24.20 theme: Raleigh
Package version: 302050000
Mac OS X 10.8.5
Darwin macmore.bdtgroup.local 12.5.0 Darwin Kernel Version 12.5.0
Sun Sep 29 13:33:47 PDT 2013
I set KeyEquivalent as "\r" on a button, and I am inputting something in the text field, the application will crash very frequently if there is a backend thread running. While if there is no backend thread running, the application will not crash when I am inputting something in the text field.
Could you please provide us exact test steps you followed. If possible please
attach a small complete project that demonstrates this behavior.
Also can you please add the logs from the following places?:
On XS IDE Log Location: XS>Help> Open Log Directory> IDE.log file (with latest
With the latest Xamarin.Mac as blow, this problem will not occur any longer.
By the way, can you give me the possible bug ID in the bugzilla that fixes this issue?
Version 5.2.1 (build 1)
Mono 3.6.0 ((no/f540f8a)
GTK+ 2.24.23 (Raleigh theme)
Package version: 306000039
Apple Developer Tools
Xcode 5.1.1 (5085)
We don't have specific bug ID for this. On going improvements by developers on xam.mac build might have fixed it internally.
Also as per comment 2 , closing this bug. Please reopen this bug if you encounter this problem in future.