Bug 16984 - Crash in OpenTK
Summary: Crash in OpenTK
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-29 10:18 UTC by Grigory (Playtika)
Modified: 2017-06-27 17:09 UTC (History)
5 users (show)

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-29 10:18:30 UTC
OpenTK.Platform.Android.EglException: EglSwapBuffers failed with error 12291 (0x3003)
  at OpenTK.Platform.Android.AndroidGraphicsContext.Swap () [0x00000] in <filename unknown>:0 
  at OpenTK.Platform.Android.AndroidGameView.SwapBuffers () [0x00000] in <filename unknown>:0 
  at Monosyne.Android.GLView.SwapBuffers () [0x00000] in <filename unknown>:0 
  at Monosyne.Android.AndroidGraphicsAdapter.SwapBuffers () [0x00000] in <filename unknown>:0 
  at Monosyne.Splash.DrawImmediately () [0x00000] in <filename unknown>:0 

1. SoftwinerEvb (dunno what is it :))
2. Motorola XT914
3. A13-MID
4. ZTE Z992
5. MID_Robin
Comment 1 Jonathan Pryor 2014-03-27 12:59:04 UTC
Could you please provide a test case?
Comment 2 Radek Doulik 2014-03-27 16:09:49 UTC
I think this might happen if your GL context is not set as current. You might try to call instance method view.MakeCurrent () on your AndroidGameView instance in Monosyne.Splash.DrawImmediately.

If it is not the case please give us a test case as Jonathan suggested, so that I can look into it.
Comment 3 Chris Hardy [MSFT] 2017-06-27 17:09:07 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!