Bug 16973 - OpenTK crash
Summary: OpenTK crash
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.10.1
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Radek Doulik
Depends on:
Reported: 2013-12-27 11:07 UTC by Grigory (Playtika)
Modified: 2017-08-23 21:11 UTC (History)
4 users (show)

Tags: bb
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:

Description Grigory (Playtika) 2013-12-27 11:07:36 UTC

I see many crashes in Hockeyapp with same stacktrace.

System.NullReferenceException: Object reference not set to an instance of an object
at OpenTK.Platform.Android.AndroidGameView.SurfaceChanged (Android.Views.ISurfaceHolder,Android.Graphics.Format,int,int) <0x001f4>
at Android.Views.ISurfaceHolderCallbackInvoker.n_SurfaceChanged_Landroid_view_SurfaceHolder_III (intptr,intptr,intptr,int,int,int) <0x0008f>
at (wrapper dynamic-method) object.54bcf56a-8f64-44b7-bd18-1035cc1787a1 (intptr,intptr,intptr,int,int,int) <0x0006b>

I suppose that holder is null in some specific cases (something related with suspend/resume cycle).

What could it be ?
Comment 1 Grigory (Playtika) 2013-12-29 10:11:33 UTC
I see it quite often on Kyocera c5155 and some small LG/Samsung devices. Also some unnamed chineese androids without normal brand name were seen in logs
Comment 2 Tom Opgenorth 2017-06-29 19:28:17 UTC
Thank you for taking the time to submit the bug. We are unable to reproduce this issue. Please attach a reproduction to the bug by starting with a clean Xamarin.Android project and adding just the code necessary to demonstrate the issue.
Comment 3 Cody Beyer (MSFT) 2017-08-23 21:11:50 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!