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.
Making a reference to any predefined NSColor object (like NSColor.Black) seems to trigger loading of the fonts.conf file from from /Library/Frameworks/Mono.framework/Versions/Current/etc. When running the packaged product on a machine which doesn't have mono installed (and of corse none of the Xamarin related software and platorms) the following line is spit on the console when it hits the first line referencing a predefined static color from NCColor:
Fontconfig error: Cannot load default config file
After the message, the process consumes a lot of cpu power for a while (even up to a minute on some machines) then the app continues to work normally and any further references to static predefined colors in NSColor don't block the running thread anymore.
To test this just make a very simple mac project and reference NSColor.Black (or whatever color you want) from a variable, then compile and try to run on a mac without mono on it (or temporarily move the fonts.conf file to some other location so you can actually debug this).
Please excuse my haste in writing the description, I made a big mistake:
Any NSColor must be read as "Color" from the System.Drawing namespace
I beleive this bug is a duplicate of bug 17225 and bug 20210.
*** This bug has been marked as a duplicate of bug 17225 ***