2 Replies Latest reply on Jan 23, 2013 7:04 PM by Bryan Laipple

    ADF Mobile: Problems Running on Samsung Galaxy S3

    Bryan Laipple
      I am observing seemingly random segment fault errors while running an ADF Mobile app on my Galaxy S3 running 4.1.1. These errors are NOT observed running the same build on:
      Android emulator (running either 4.0.3, 4.1.2, 4.2)
      Galaxy Nexus running 4.1.1
      Nexus 7 tablet 4.2.1
      iPhone 4S

      The app will usually just get killed and I use logcat over ADB to see the fault and each time occurs in a different location in the code. Here are some examples:
      01-17 11:42:36.558 9366 9463 D CVM : Java Frame java.lang.String.<init>([CII)V(String.java:197)
      01-17 12:37:41.956 12045 12381 D CVM : JNI Frame java.lang.Class.getConstructor0([Ljava/lang/Class;I)Ljava/lang/reflect/Constructor;(Native Method)
      01-17 12:41:03.781 12740 12884 D CVM     :   JNI Frame         java.lang.Class.forName0(Ljava/lang/String;ZLjava/lang/ClassLoader;)Ljava/lang/Class;(Native Method)
      01-17 12:44:00.286 13203 13315 D CVM     :   Java Frame        java.util.Hashtable.get(Ljava/lang/Object;)Ljava/lang/Object;(Hashtable.java:355)

      In addition to the application just being killed, it will sometimes remain alive, but after throwing some odd exceptions such as:
      java.util.MissingResourceException: Can't find bundle for base name oracle.adfmf.resource.CDCErrorBundle

      These errors make me think some of the application is being corrupting in memory.  I have looked at the CVM runtime heap space and there is plenty of free space so I don't see that as the heap is the culprit.

      It should be noted that this was observed only after making a change to use concurrent threads to update data from HTTPS web responses.  The problems are seen even if only 1 thread is running the update, but if I serialize the behavior in the main thread I'm not seeing the issue.

      The thought here in the office is that there must be something specific with the ROM Samsung distributes for the S3 that makes it behave differently.  I even tested a second S3 to make sure it wasn't my particular phone and saw the same issues.


      JDev build: JDEVADF_11.
      ADF Mobile:
      OS: Windows 7
      Device Model: Samsung Galaxy S3 SCH-I535
      Android Version: 4.1.1
      Android Debug Bridge Version: 1.0.29