Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6713025
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T08:19:49+00:00 2026-05-26T08:19:49+00:00

I know this is something i should have learned before switching to opengl es

  • 0

I know this is something i should have learned before switching to opengl es 1.0 from software drawing, but I’ve been unable to find any information on the subject…

My opengl app crashes after going to sleep if nothing is touched for a while… I’m wondering if it’s because i’m not unloading textures or vertex/colour/texture/index buffers before it goes to sleep… I’m really unsure on how to do this or even if it would help… could someone direct me to or tell me a quick guide to the rules of what has to be reloaded, destroyed and so on? I’m really confused by all this…

I dunno if it’s helpful, but my main class extends GLSurfaceView and implements "Renderer", which loads all the textures and buffer objects in onScreenCreated and fixes the screen scaling on onSurfaceChanged. In the main activity (which is where the main class is linked in) overides onResume and onPause calling the onResume and onPause openGL surface commands…

Any clue to what might be wrong would be very helpful… My game engine is halfway coded but I’m worried that a glitch like this will just halt my current and future projects.

I’m using Froyo (android 2.2) and openGL ES 1.0.

error print out from logcat:

10-24 03:13:41.988: ERROR/AndroidRuntime(9888): FATAL EXCEPTION: GLThread 26

10-24 03:13:41.988: ERROR/AndroidRuntime(9888): java.lang.IllegalThreadStateException: Thread already started.

10-24 03:13:41.988: ERROR/AndroidRuntime(9888): at java.lang.Thread.start(Thread.java:1322)

10-24 03:13:41.988: ERROR/AndroidRuntime(9888): at or.gl.m5.Screen.onSurfaceCreated(Screen.java:161)

10-24 03:13:41.988: ERROR/AndroidRuntime(9888): at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1317)

10-24 03:13:41.988: ERROR/AndroidRuntime(9888): at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1116)

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T08:19:49+00:00Added an answer on May 26, 2026 at 8:19 am

    Without seeing a stack trace or what kind of exception it throws out it is kind of hard to say something. But anyway I’m throwing a wild guess that it crashes because you have to reload textures after your activity is resumed. The textures you have previously created become invalid once your view goes to background.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I feel like this is something I should already know, but I'm just not
I get the feeling this is probably something I should know but I can't
This is something stupid I probably should know, but Googling fails me: When compiling
I feel like I should know this but I've been stumped for hours now
This is something I should have cleared up long ago, but I just need
This seems like it should be something I already know. We need to run
I know this isn't strictly speaking a programming question but something I always hear
This is something I encounter frequently, but I don't know the elegant way of
I know this sounds stupid, but look at this simple example (working dir should
I know this is something easy that is just eluding me. Anyway, I have

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.