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.
And the decompiled code is ... very strange.
Width is int, but setter casts it to nint.
private nint HeightIntPtr;
private nint WidthIntPtr;
private nint RowBytesCountIntPtr;
public int Width
return (int) this.WidthIntPtr;
this.WidthIntPtr = (nint) value;
This is by design; it is highly doubtful you'll ever need Height/Width/BytesPerRow > int32.MaxValue, so we've bound it using the 32-bit data types.
why didn't Apple thought of this then ?
You are creating a potential limitation to Apple's version because you decided to.
If tomorrow Apple's decide to put specific information in the unused high bits of the 64 bit value, what will happen ? Your customers will be stuck until you fix it.
This is not a good direction to follow.