Bug 4644 - OpenTK apps crash on startup with "EglCreateWindowSurface failed with error 12288 (0x3000)"
Summary: OpenTK apps crash on startup with "EglCreateWindowSurface failed with error 1...
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.0
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-04-25 12:13 UTC by Andreia Gaita
Modified: 2012-04-25 13:17 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Andreia Gaita 2012-04-25 12:13:20 UTC
In OpentK, creating a window surface with the default GraphicsMode settings fails on certain devices (Samsung in particular). The error code is 12288 (success). These devices seem to return invalid graphics configurations in the first entries of the list return from EglChooseConfig for any requested configuration, which defeats the purpose of asking the device for valid configurations.

logcat includes the error "EglCreateWindowSurface failed with error 12288 (0x3000)", and the app crashes.
Comment 2 Andreia Gaita 2012-04-25 13:17:39 UTC
This should be fixed in master/ffc8ddb and 4.0-series/aa10a57