java.lang.NullPointerException

JIRA | Raphael Kubo da Costa | 1 year ago
  1. 0

    [Pull request #3068|https://github.com/crosswalk-project/crosswalk/pull/3068] and its respective commit "Refactored shared mode and refined the interface" has introduced a regression that causes a random subset of the RuntimeClient and RuntimeEmbeddedClient tests to fail. The failures can be seen [here in the builder information|https://build.crosswalk-project.org/builders/Crosswalk%20Tests%20%28Android%20x86%29], but it only makes sense to look at the failures with [the Android x86 builder information|https://build.crosswalk-project.org/builders/Crosswalk%20Android-X86], as the latter has been suffering from disk space issues and some builds do not get processed by the machine running the device tests. The backtrace generally looks like this: {code} E/AndroidRuntime(32124): FATAL EXCEPTION: main E/AndroidRuntime(32124): java.lang.NullPointerException E/AndroidRuntime(32124): at org.xwalk.test.util.XWalkRuntimeClientTestGeneric$1.run(XWalkRuntimeClientTestGeneric.java:35) E/AndroidRuntime(32124): at android.app.Instrumentation$SyncRunnable.run(Instrumentation.java:1679) E/AndroidRuntime(32124): at android.os.Handler.handleCallback(Handler.java:756) E/AndroidRuntime(32124): at android.os.Handler.dispatchMessage(Handler.java:101) E/AndroidRuntime(32124): at android.os.Looper.loop(Looper.java:152) E/AndroidRuntime(32124): at android.app.ActivityThread.main(ActivityThread.java:5691) E/AndroidRuntime(32124): at java.lang.reflect.Method.invokeNative(Native Method) E/AndroidRuntime(32124): at java.lang.reflect.Method.invoke(Method.java:511) E/AndroidRuntime(32124): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793) E/AndroidRuntime(32124): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560) E/AndroidRuntime(32124): at dalvik.system.NativeStart.main(Native Method) W/ActivityManager( 2175): Error in app org.xwalk.runtime.client.shell running instrumentation ComponentInfo{org.xwalk.runtime.client.test/android.test.InstrumentationTestRunner}: W/ActivityManager( 2175): java.lang.NullPointerException W/ActivityManager( 2175): java.lang.NullPointerException {code} [~whz] did mention something like this in his last comment in that pull request, but I do not see any follow-up to that. We need to get this fixed as soon as possible, as otherwise it is difficult to both update our M44 version as well as move to M45 in the future (we need all tests to be passing to verify that the updates to not introduce regressions).

    JIRA | 1 year ago | Raphael Kubo da Costa
    java.lang.NullPointerException
  2. 0

    [Pull request #3068|https://github.com/crosswalk-project/crosswalk/pull/3068] and its respective commit "Refactored shared mode and refined the interface" has introduced a regression that causes a random subset of the RuntimeClient and RuntimeEmbeddedClient tests to fail. The failures can be seen [here in the builder information|https://build.crosswalk-project.org/builders/Crosswalk%20Tests%20%28Android%20x86%29], but it only makes sense to look at the failures with [the Android x86 builder information|https://build.crosswalk-project.org/builders/Crosswalk%20Android-X86], as the latter has been suffering from disk space issues and some builds do not get processed by the machine running the device tests. The backtrace generally looks like this: {code} E/AndroidRuntime(32124): FATAL EXCEPTION: main E/AndroidRuntime(32124): java.lang.NullPointerException E/AndroidRuntime(32124): at org.xwalk.test.util.XWalkRuntimeClientTestGeneric$1.run(XWalkRuntimeClientTestGeneric.java:35) E/AndroidRuntime(32124): at android.app.Instrumentation$SyncRunnable.run(Instrumentation.java:1679) E/AndroidRuntime(32124): at android.os.Handler.handleCallback(Handler.java:756) E/AndroidRuntime(32124): at android.os.Handler.dispatchMessage(Handler.java:101) E/AndroidRuntime(32124): at android.os.Looper.loop(Looper.java:152) E/AndroidRuntime(32124): at android.app.ActivityThread.main(ActivityThread.java:5691) E/AndroidRuntime(32124): at java.lang.reflect.Method.invokeNative(Native Method) E/AndroidRuntime(32124): at java.lang.reflect.Method.invoke(Method.java:511) E/AndroidRuntime(32124): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793) E/AndroidRuntime(32124): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560) E/AndroidRuntime(32124): at dalvik.system.NativeStart.main(Native Method) W/ActivityManager( 2175): Error in app org.xwalk.runtime.client.shell running instrumentation ComponentInfo{org.xwalk.runtime.client.test/android.test.InstrumentationTestRunner}: W/ActivityManager( 2175): java.lang.NullPointerException W/ActivityManager( 2175): java.lang.NullPointerException {code} [~whz] did mention something like this in his last comment in that pull request, but I do not see any follow-up to that. We need to get this fixed as soon as possible, as otherwise it is difficult to both update our M44 version as well as move to M45 in the future (we need all tests to be passing to verify that the updates to not introduce regressions).

    JIRA | 1 year ago | Raphael Kubo da Costa
    java.lang.NullPointerException
  3. 0

    [Pull request #3068|https://github.com/crosswalk-project/crosswalk/pull/3068] and its respective commit "Refactored shared mode and refined the interface" has introduced a regression that causes a random subset of the RuntimeClient and RuntimeEmbeddedClient tests to fail. The failures can be seen [here in the builder information|https://build.crosswalk-project.org/builders/Crosswalk%20Tests%20%28Android%20x86%29], but it only makes sense to look at the failures with [the Android x86 builder information|https://build.crosswalk-project.org/builders/Crosswalk%20Android-X86], as the latter has been suffering from disk space issues and some builds do not get processed by the machine running the device tests. The backtrace generally looks like this: {code} E/AndroidRuntime(32124): FATAL EXCEPTION: main E/AndroidRuntime(32124): java.lang.NullPointerException E/AndroidRuntime(32124): at org.xwalk.test.util.XWalkRuntimeClientTestGeneric$1.run(XWalkRuntimeClientTestGeneric.java:35) E/AndroidRuntime(32124): at android.app.Instrumentation$SyncRunnable.run(Instrumentation.java:1679) E/AndroidRuntime(32124): at android.os.Handler.handleCallback(Handler.java:756) E/AndroidRuntime(32124): at android.os.Handler.dispatchMessage(Handler.java:101) E/AndroidRuntime(32124): at android.os.Looper.loop(Looper.java:152) E/AndroidRuntime(32124): at android.app.ActivityThread.main(ActivityThread.java:5691) E/AndroidRuntime(32124): at java.lang.reflect.Method.invokeNative(Native Method) E/AndroidRuntime(32124): at java.lang.reflect.Method.invoke(Method.java:511) E/AndroidRuntime(32124): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793) E/AndroidRuntime(32124): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560) E/AndroidRuntime(32124): at dalvik.system.NativeStart.main(Native Method) W/ActivityManager( 2175): Error in app org.xwalk.runtime.client.shell running instrumentation ComponentInfo{org.xwalk.runtime.client.test/android.test.InstrumentationTestRunner}: W/ActivityManager( 2175): java.lang.NullPointerException W/ActivityManager( 2175): java.lang.NullPointerException {code} [~whz] did mention something like this in his last comment in that pull request, but I do not see any follow-up to that. We need to get this fixed as soon as possible, as otherwise it is difficult to both update our M44 version as well as move to M45 in the future (we need all tests to be passing to verify that the updates to not introduce regressions).

    JIRA | 1 year ago | Raphael Kubo da Costa
    java.lang.NullPointerException
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    [Pull request #3068|https://github.com/crosswalk-project/crosswalk/pull/3068] and its respective commit "Refactored shared mode and refined the interface" has introduced a regression that causes a random subset of the RuntimeClient and RuntimeEmbeddedClient tests to fail. The failures can be seen [here in the builder information|https://build.crosswalk-project.org/builders/Crosswalk%20Tests%20%28Android%20x86%29], but it only makes sense to look at the failures with [the Android x86 builder information|https://build.crosswalk-project.org/builders/Crosswalk%20Android-X86], as the latter has been suffering from disk space issues and some builds do not get processed by the machine running the device tests. The backtrace generally looks like this: {code} E/AndroidRuntime(32124): FATAL EXCEPTION: main E/AndroidRuntime(32124): java.lang.NullPointerException E/AndroidRuntime(32124): at org.xwalk.test.util.XWalkRuntimeClientTestGeneric$1.run(XWalkRuntimeClientTestGeneric.java:35) E/AndroidRuntime(32124): at android.app.Instrumentation$SyncRunnable.run(Instrumentation.java:1679) E/AndroidRuntime(32124): at android.os.Handler.handleCallback(Handler.java:756) E/AndroidRuntime(32124): at android.os.Handler.dispatchMessage(Handler.java:101) E/AndroidRuntime(32124): at android.os.Looper.loop(Looper.java:152) E/AndroidRuntime(32124): at android.app.ActivityThread.main(ActivityThread.java:5691) E/AndroidRuntime(32124): at java.lang.reflect.Method.invokeNative(Native Method) E/AndroidRuntime(32124): at java.lang.reflect.Method.invoke(Method.java:511) E/AndroidRuntime(32124): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793) E/AndroidRuntime(32124): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560) E/AndroidRuntime(32124): at dalvik.system.NativeStart.main(Native Method) W/ActivityManager( 2175): Error in app org.xwalk.runtime.client.shell running instrumentation ComponentInfo{org.xwalk.runtime.client.test/android.test.InstrumentationTestRunner}: W/ActivityManager( 2175): java.lang.NullPointerException W/ActivityManager( 2175): java.lang.NullPointerException {code} [~whz] did mention something like this in his last comment in that pull request, but I do not see any follow-up to that. We need to get this fixed as soon as possible, as otherwise it is difficult to both update our M44 version as well as move to M45 in the future (we need all tests to be passing to verify that the updates to not introduce regressions).

    JIRA | 1 year ago | Raphael Kubo da Costa
    java.lang.NullPointerException
  6. 0

    Android: Saving Map State in Google map

    Stack Overflow | 11 months ago | Junie Negentien
    java.lang.RuntimeException: Unable to resume activity {com.ourThesis.junieNegentien2015/com.ourThesis.junieNegentien2015.MainActivity}: java.lang.NullPointerException

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.NullPointerException

      No message provided

      at org.xwalk.test.util.XWalkRuntimeClientTestGeneric$1.run()
    2. org.xwalk.test
      XWalkRuntimeClientTestGeneric$1.run
      1. org.xwalk.test.util.XWalkRuntimeClientTestGeneric$1.run(XWalkRuntimeClientTestGeneric.java:35)
      1 frame
    3. Android Platform
      ActivityThread.main
      1. android.app.Instrumentation$SyncRunnable.run(Instrumentation.java:1679)
      2. android.os.Handler.handleCallback(Handler.java:756)
      3. android.os.Handler.dispatchMessage(Handler.java:101)
      4. android.os.Looper.loop(Looper.java:152)
      5. android.app.ActivityThread.main(ActivityThread.java:5691)
      5 frames
    4. Java RT
      Method.invoke
      1. java.lang.reflect.Method.invokeNative(Native Method)
      2. java.lang.reflect.Method.invoke(Method.java:511)
      2 frames
    5. Android
      ZygoteInit.main
      1. com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
      2. com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
      2 frames
    6. Android Platform
      NativeStart.main
      1. dalvik.system.NativeStart.main(Native Method)
      1 frame