Bug 6601 - GLCube example freezes after 10-20 minutes, GLNativeES20 doesn't, Bug in AndroidGameView?
Summary: GLCube example freezes after 10-20 minutes, GLNativeES20 doesn't, Bug in Andr...
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.2.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2012-08-19 03:30 UTC by Heiko
Modified: 2014-12-05 07:20 UTC (History)
2 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 Heiko 2012-08-19 03:30:49 UTC
The examples GLCube, GLCube-1.0, GLTriangle20, GLTriangle20-1.0 freeze after running for about 10 - 20 minutes. I'm using a Toshiba AT200 tablet running Android 4.0.3 and Mono for Android 4.2.4. The freeze seems to happen in the class library, the user code is executing without freezing or throwing exeptions. The example GLNativeES20 doesn't freeze, so it looks like a bug in AndroidGameView/OpenTK.
Comment 1 dean.ellis 2014-12-02 10:59:23 UTC
I am unable to replicate this on the latest version of OpenTK-1. Its possible that one of the recent changes to the AndroidGameView has fixed this issue.
Comment 2 dean.ellis 2014-12-05 07:20:42 UTC
The samples run file on the devices I have available so I cannot reproduce this issue. Its possible that recent changes to the AndroidGameView have fixed it.