2.7.7.1 XPRIZE java.lang.RuntimeException: An error occurred while executing doInBackground()

[JackMostow]

Jo Grimstad [8:01 AM] 11/27/2018:

We also see several occurrences of this one:
CRASH_20000101_154620_5B20001354_release_2.7.7.1.txt
java.lang.RuntimeException: An error occurred while executing doInBackground()
--------- Stack trace ---------
android.os.AsyncTask$3.done(AsyncTask.java:325)
java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
java.util.concurrent.FutureTask.setException(FutureTask.java:223)
java.util.concurrent.FutureTask.run(FutureTask.java:242)
android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:243)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
java.lang.Thread.run(Thread.java:761)

--------- Cause ---------
java.lang.NullPointerException: Attempt to get length of null array
cmu.xprize.robotutor.tutorengine.CTutorAssetManager.listFolder(CTutorAssetManager.java:228)
cmu.xprize.robotutor.tutorengine.CTutorAssetManager.updateAssetPackages(CTutorAssetManager.java:552)
cmu.xprize.robotutor.RoboTutor$tutorConfigTask.doInBackground(RoboTutor.java:478)
cmu.xprize.robotutor.RoboTutor$tutorConfigTask.doInBackground(RoboTutor.java:431)
android.os.AsyncTask$2.call(AsyncTask.java:305)
java.util.concurrent.FutureTask.run(FutureTask.java:237)
android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:243)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
java.lang.Thread.run(Thread.java:761)

[JackMostow]

Is CRASH_20000101_154620_5B20001354_release_2.7.7.1.txt related to battery exhaustion?

[kevindeland]

The code where this is occurring is 2 years old. Not sure what is happening.

See blame here.

[JackMostow]

1. Could it be due to some difference in the OS version or build between the tablets XPRIZE is using and the ones we installed and tested RoboTutor on?

2. 2.7.7.1 has many logs but only one CRASH log from Bagamoyo so far, in SAMSUNG - R52JA18WFEY:
   CRASH_20181116_181459_52009e8afef694ad_release_2.7.7.1.txt, due to java.lang.OutOfMemoryError: pthread_create (1040KB stack) failed: Try again.

3. Bagamoyo PIXEL TREE 5B02000315 is our only Pixel at a beta site with logs for 2.7.7.1. They date back to Nov. 4 but it has no CRASH logs.

4. What precise OS version and build are on:
   a. the tablet(s) you tested on?
   b. the tablet(s) VMC tested on?
   c. the tablet(s) that Jo installed on?
   d. the tablet(s) at XPRIZE sites?

5. What information should we request from Jo about 4c and 4d to investigate the hypothesis that the crashes are due to a difference from 4a and 4b?

If there's any possibility that the crashes are due to such a discrepancy, we should find out ASAP and determine whether it's reasonable to expect XPRIZE to fix it -- and desirable, given how long it would take kids to start over and get back to their proper levels.