What steps will reproduce the problem?
1. Run Arity
2. Show 3D graph (i.e. x/y)
3. Exit with back button
What is the expected output? What do you see instead?
I expect it to just exit and be gone. Instead, it exits, but the system
crawls (this is on a Nexus One; when it crawls, you KNOW something's wrong)
and a system monitor such as htop reports that arity is at ~90% CPU. After
killing arity's process, things return to normal.
What version of the product are you using? On what operating system?
Nexus One with CyanogenMod 5.0.4.1
Please provide any additional information below.
logcat:
D/Calculator( 1381): onResume calculator.Graph3dView@45ef9be0
D/Calculator( 1381): onResume calculator.Graph3dView@45ef9be0
D/Calculator( 1381): surfaceCreated calculator.Graph3dView@45ef9be0
D/Calculator( 1381): surfaceChanged -1 calculator.Graph3dView@45ef9be0
D/libEGL ( 1381): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 1381): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 1381): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 1381): loaded /system/lib/egl/libGLESv2_adreno200.so
D/Calculator( 1381): VBOs support: true version OpenGL ES-CM 1.1
D/Calculator( 1381): update VBOs 1 2 3
D/Calculator( 1381): Graph3d update
D/Calculator( 1381): f/s 0
I/ActivityManager( 92): Displayed activity
arity.calculator/calculator.Calculator: 415 ms (total 415 ms)
D/Calculator( 1381): f/s 48
D/Calculator( 1381): f/s 60
D/Calculator( 1381): f/s 60
D/Calculator( 1381): f/s 58
W/KeyCharacterMap( 1381): No keyboard for id 65540
W/KeyCharacterMap( 1381): Using default keymap:
/system/usr/keychars/qwerty.kcm.bin
D/Calculator( 1381): onPause calculator.Graph3dView@45ef9be0
V/RenderScript_jni( 176): surfaceCreated
V/RenderScript_jni( 176): surfaceChanged
V/RenderScript( 176): setSurface 480 762 0x3a13d8
W/InputManagerService( 92): Starting input on non-focused client
com.android.internal.view.IInputMethodClient$Stub$Proxy@4600be78 (uid=10054
pid=1381)
D/Calculator( 1381): surfaceDestroyed calculator.Graph3dView@45ef9be0
Original issue reported on code.google.com by nat.ho...@gmail.com on 8 Mar 2010 at 12:54
Original issue reported on code.google.com by
nat.ho...@gmail.com
on 8 Mar 2010 at 12:54