Bug 12472 - UIImage.AsPNG and .AsJPEG(float) calls EnsureUIThread
Summary: UIImage.AsPNG and .AsJPEG(float) calls EnsureUIThread
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 6.2.x
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-05-30 07:34 UTC by folex
Modified: 2013-06-03 18:16 UTC (History)
2 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 FIXED

Description folex 2013-05-30 07:34:45 UTC
It changed in Xamarin.iOS 6.2.6. But such UIKit function usually thread safe and these aren't exceptions. 
So, why ensuring UI thread?
Comment 1 Sebastien Pouliot 2013-05-30 08:20:49 UTC
We had a discussion with Apple engineers about the selectors/functions we marked as [ThreadSafe]. It turns out a few of them were wrong, i.e. not thread-safe. AsJPEG being one of them.
Comment 2 folex 2013-05-30 14:30:16 UTC
Sad. Do you know any case when AsJPEG or AsPNG will show it's "thread-not-safety"? Just curious. 
Thanks for response anyway.
Comment 3 Sebastien Pouliot 2013-05-30 15:28:43 UTC
After re-reading the emails I found out the answer was filtered, i.e. some items* were removed to show us only the non-thread safe methods/selectors.

* exactly those two UIImagePNGRepresentation and UIImageJPEGRepresentation - but I'll re-read the whole email thread again to be 100% sure we did not make another mistake.

Thanks a lot for reporting and asking details :-)

fixed in 9994a9dee8b65f0631cd260627e0d7fbb5a93d0c
Comment 4 Miguel de Icaza [MSFT] 2013-06-03 18:16:50 UTC
As Sebastien discovered, I misread the email, and those methods are thread safe.

A fix is now available on the stable channel.