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.
The following code is unsafe, because the GC is free to move the 'values' array once we're out of the fixed statement:
fixed (nfloat *ptr = values)
return (IntPtr) ptr;
this means that the calling function now has pointer to memory that the GC can move at any time.
Raising priority and targeting the next release (15.6), since this will cause random crashes (or other random behavior) when it occurs, and it will be very tricky to track down.
The manual bindings for CIVector has the same code.
CIVector fixed in https://github.com/xamarin/xamarin-macios/pull/3038
@Alex since you're working on MPS can you apply the same pattern on MPSKernel ? thanks!
Switching milestone to `xcode9.2` since it enables the framework on macOS (and will likely be merged into 15.5)
Fixed in xamarin-macios/xcode9.2 @ https://github.com/xamarin/xamarin-macios/commit/87f9e239898c16a64de153e6fb631b7ad8fb3865