Databases
StackOverflow2013
Postsdbo
POerror after close the application
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POerror after close the application
    primarykey
    data
    text
    <p>i have a glsurfaceview renderer with some code that allows me resume after press home button and enter again on the game, and that works fine, but if i close the game with the return button, and i try enter again to the game, it crashes and close. i've tried writing finish() on OnDestroy but not work. i already checked that onDestroy() execute it when i press return button. in onSurfaceCreated i have functions that load textures and set vertices for draw those textures, but, i dont understand what could be happening</p> <p>edit:</p> <p>this is the log after i launch the game the second time, having closed it before</p> <pre><code>05-08 20:30:41.069: I/GLThread(6272): noticed surfaceView surface lost tid=12 05-08 20:30:41.069: I/GLThread(6272): onResume tid=12 05-08 20:30:41.169: I/GLThread(6272): noticed surfaceView surface acquired tid=12 05-08 20:30:41.169: W/EglHelper(6272): start() tid=12 05-08 20:30:41.219: W/EglHelper(6272): createContext com.google.android.gles_jni.EGLContextImpl@4056d398 tid=12 05-08 20:30:41.219: I/GLThread(6272): noticing that we want render notification tid=12 05-08 20:30:41.219: W/GLThread(6272): egl createSurface 05-08 20:30:41.219: W/EglHelper(6272): createSurface() tid=12 05-08 20:30:41.219: W/GLThread(6272): onSurfaceCreated 05-08 20:30:41.219: W/GLThread(6272): onSurfaceChanged(480, 320) 05-08 20:30:41.379: W/EglHelper(6272): destroySurface() tid=12 05-08 20:30:41.389: W/EglHelper(6272): finish() tid=12 05-08 20:30:41.389: W/dalvikvm(6272): threadid=9: thread exiting with uncaught exception (group=0x40018578) 05-08 20:30:41.389: E/AndroidRuntime(6272): FATAL EXCEPTION: GLThread 12 05-08 20:30:41.389: E/AndroidRuntime(6272): java.lang.NullPointerException 05-08 20:30:41.389: E/AndroidRuntime(6272): at glfg.gl.render.setverticesSquare(render.java:180) 05-08 20:30:41.389: E/AndroidRuntime(6272): at glfg.gl.render.onSurfaceChanged(render.java:475) 05-08 20:30:41.389: E/AndroidRuntime(6272): at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1381) 05-08 20:30:41.389: E/AndroidRuntime(6272): at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1138) 05-08 20:30:41.399: I/GLThread(6272): onPause tid=12 </code></pre> <p>if i kill the process, i can enter again without problems, but if i exit with return button, it crashes when i try to launch it again, it's supposed that the app would be closed totally but seems that not</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USTim
    1. USJose
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POerror after close the application
      1. This table or related slice is empty.
      1. VTUpMod
    1. CONoone else will understand what could be happening either, if you don't include the stack dump from your system log. Then again, if you examine it first, you might understand the problem -- but if not, edit your post to include it so someone might help.
      singulars
      1. POerror after close the application
      1. USmah
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload