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.
This looks like a regression caused by the fix for bnc #686045 / bxc #1366 / assistly #2687. The timesource is nullified (on stop) but can still be accessed (on suspend).
I'll rebuild a newer OpenTK.dll and attach it to the bug report. Hopefully that will fix your issue and I'll then ensure the fix gets into newer MonoTouch releases.
Created attachment 703 [details]
updated OpenTK.dll assembly
To use the attached assembly (on top of MonoTouch 5.0) do:
1) backup your /Developer/MonoTouch/usr/lib/mono/2.1/OpenTK.dll and /Developer/MonoTouch/usr/lib/mono/2.1/OpenTK.dll.mdb files
2) copy the attached file to /Developer/MonoTouch/usr/lib/mono/2.1/OpenTK.dll
3) remove the /Developer/MonoTouch/usr/lib/mono/2.1/OpenTK.dll.mdb symbols (they won't match anymore)
4) clean, rebuild and test your application
Please let me know if this fix the issue (without causing others :-). Thanks
Your fix of OpenTK.dll has corrected this issue. Per you instructions on comment 2, my application no longer crashes.
On a personal note, I want to thank you and the whole xamarin team for a great product and the fast fix to my issue.
I'm glad this fixed your issue. I'll make sure newer MT releases contain this fix.
Thanks for the confirmation!
Tested with MonoTouch sample app GLPaint - GameView. Figured transitioning between the one OpenTK view and the menu (non OpenTK) view is sufficient to test the fix. If the views must be in the same application, let me know and I can re-verify.