Bug 6093 - CLCube and Textured cube throwing exception OpenTK.Platform.Android.EglException"
Summary: CLCube and Textured cube throwing exception OpenTK.Platform.Android.EglExcept...
Status: RESOLVED DUPLICATE of bug 6684
Alias: None
Product: Android
Classification: Xamarin
Component: Samples ()
Version: 4.2.x
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-07-12 05:24 UTC by Nischal
Modified: 2012-08-24 16:27 UTC (History)
3 users (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 DUPLICATE of bug 6684

Description Nischal 2012-07-12 05:24:35 UTC
Steps to reproduce this issue:
1. Open GLCobe/Textured Cube.
2. Debug/Run the application.


Actual result:
Application crashed as well as deployed to device throwing exception  "OpenTK.Platform.Android.EglException".

Expected result:
Application should deployed to device successfully.

Supplement Info:
https://gist.github.com/3096926
Logcat info:
https://gist.github.com/3096941

Environment:
Mac and Windows
MD 3.0.3.3
MFA 4.2.4.167234518

App info:
CLCube,GLCube1.0,TexturedCube, TexturedCube1.0/master
Device info
HTC one
4.0.3
Debug Vs Release: This is happening on both debug and release.

Regression status:
This is not happening whit MD 3.0.3.2 and MFA 4.2.3

Note: This is not happening with Beta 4.2.4.122434861
Comment 1 PJ 2012-07-12 14:15:24 UTC
Please report on the full extent of the devices affected. Was this only reproducible on the HTC one? If the issue happens on all devices it is of much different severity than if it only happens on one.
Comment 2 PJ 2012-07-12 15:17:30 UTC
Also - please be sure that this issue is continuously reproducible (after uninstalling and re-installing all mono products.

For the record, I cannot reproduce this issue on an Acer Iconiatab A200 with 4.0.3 or a Verizon Galaxy Nexus with 4.0.4

I tried with the build target set to both 8 and 15.
Comment 3 PJ 2012-07-12 15:23:34 UTC
One last thing to try for additional information - 

There are two GLDiagnostic sample apps in the monodroid-samples repository. Please run these samples and provide the application output here as a gist.

We will add doing this as a test case so this information is always on hand after a test run.
Comment 4 PJ 2012-07-12 19:55:22 UTC
*** Bug 5951 has been marked as a duplicate of this bug. ***
Comment 5 PJ 2012-07-12 19:57:15 UTC
CORRECTION: This is not a duplicate of 5951.
Comment 6 Nischal 2012-07-13 07:29:40 UTC
Regarding Comment #2:

When try to Debug GLCube after setting the target framework 4.0.3 through Project Options, and try to Debug the application on the Device HTC One (4.0.3), it gives the same error mentioned in the bug above.

However, when we try to run the same application after setting the target framework 4.0.3 through Project Options, and try to Debug the application on the Device Nexus (4.0.4) the application is working fine, as it launch successfully without throwing any exception.


Also, when try to Debug GLCube after setting the Target Framework set as 2.2 through Project Options, on the Device HTC One (4.0.3), it gives the error "Failed to Install Platform Framework". Below are the supplement information for the same:

Deploy to Device logs: https://gist.github.com/3104359
Logcat: https://gist.github.com/3104353

And a different bug has been reported: 5951 for all the applications having target framework as 2.2 getting deployed on HTC One (4.0.3). However, in the bug 5951 this information is missing.
Comment 7 Nischal 2012-07-13 07:49:33 UTC
One more additional update regarding Comment #6 : when try to Debug GLCube after setting the Target Framework set as 2.2 through Project Options, on the Device Nexus (4.0.4), it is working fine as it launch successfully without throwing any exception.

Regarding Comment #3

GL Diagnostic-1.0 (same behavior on both HTC One 4.0.3 & Nexus 4.0.4)

Application launches successfully, a Black blank screen appears user can do nothing. 

The logcat as well as the application output is below

Application output: https://gist.github.com/3104431
Logcat: https://gist.github.com/3104446

GL Diagnostics (same behavior on both HTC One 4.0.3 & Nexus 4.0.4)

Application launches successfully, a Black blank screen appears user can do nothing. 

The logcat as well as the application output is below

Application Output: https://gist.github.com/3104469
Logcat: https://gist.github.com/3104467
Comment 8 Jonathan Pryor 2012-07-13 17:10:47 UTC
This makes little sense; as per the original description:

> Note: This is not happening with Beta 4.2.4.122434861

while it's reported as failing in 4.2.4.167234518.

The only changes between those two versions lie in the Visual Studio extension, which shouldn't be implicated here.

Question: Which API level is the application targeting? If you set the project's TargetFrameworkVersion to Android v4.0 or later, this is very probably a repeat of #5715 and the default enabling of hardware acceleration is causing things to break:

https://bugzilla.xamarin.com/show_bug.cgi?id=5715#c6

Rephrased: does it still crash if the TargetFrameworkVersion is set to 8 (or something < 14)?
Comment 9 Nischal 2012-07-17 04:09:56 UTC
We re-checked and it was also reproducible on MFA 4.2.4.122434861

Issue occurs with target framework set to 4.0.3
Comment 10 Jonathan Pryor 2012-07-17 11:19:29 UTC
If the issue occurs with TargetFrameworkVersion set to 4.0.3 (which you stated in Comment #9), then it's likely a duplicate of Bug #5715 (which I stated in Comment #8).

If you set TargetFrameworkVersion to Android v2.2, does it still crash?
Comment 11 PJ 2012-07-17 14:16:45 UTC
The 360 team is having problems getting consistent results. They just told me this morning that after re-trying, they can reproduce the issue on all Target Frameworks.

This new reported behavior, however, directly contradicts the behavior reported in Comment 6 (where they  at least could not deploy to the device with the target framework set to 2.2).


In addition, it seems that they are having the issue where the GUI is lying about which packages are installed.  They had been removing all the packages between each deploy, but then I had them remove the packages and check with adb.

After using the GUI to remove all the applications, and then running

adb shell
pm list packages -f

They got https://gist.github.com/3130440

Which includes all the MFA packages.  


I'll work with them to properly reset the environment and re-check.
Comment 12 Nischal 2012-08-08 07:47:17 UTC
This issue still exists with the New Builds of MFA and MD:

Environment:
MD 3.0.4.3 a4a635018f425d71a253d39114d945c4d6f7cbdb
MFA-4.2.5.219693106 d184032a5a1f02686f8546427ce94f2a54ec7935

Device info:
HTC One (4.0.3) and Samsung Galaxy Tab 10.1 (4.0.3)

Application information:
master branch: xamarin-monodroid-samples-2f0726f1a0

The error and the stack trace everything is the same as it was mentioned in the original issue.
Comment 13 Nischal 2012-08-21 07:09:00 UTC
This issue also exists with the latest build:

MFA 4.2.5 - 1c171b953c83a42cddae887e71592f7fd967d3c1
MD 3.0.4.4 - d70c0215a4e81cb9d7a318f9469b1227ad3d0407

Device info:
Nexus 4.1 JellyBean

Environment info:
All Mac and All Windows.

The error and the stack trace everything is the same as it was mentioned in the
original issue.

Also, below is the MD logs and Android tool logs for the same:

MD logs: https://gist.github.com/3414554
Android tool logs: https://gist.github.com/3414558
Comment 14 PJ 2012-08-23 00:59:30 UTC
So to clarify - is the bug still reproducible on all of the mentioned devices, or is it now restricted to the Nexus?

And is it consistently reproducible on all target frameworks or just the ones you mentioned in comment 7?
Comment 15 PJ 2012-08-24 16:27:21 UTC
This bug is getting very convoluted, so I've separated out the issues. Bug 5715 will track the actual underlying AndroidGameView issue, and bug 6684 will track the changes needed to work around the problem going forward.


I am marking this bug as a duplicate of the new, concise bug 6684 so that the information remains linked.

*** This bug has been marked as a duplicate of bug 6684 ***