java.lang.NullPointerException: monitorEnter called on a null object

Terracotta | jflesh | 8 years ago
  1. 0

    "monitorEnter called on a null object"

    Terracotta | 8 years ago | jflesh
    java.lang.NullPointerException: monitorEnter called on a null object
  2. 0
    samebug tip
    The resource was accessed after it was dismissed.
  3. 0
    samebug tip
    You can't use hide() or remove() or many things with NULL values, try checking for NULL before calling this methods.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0
    samebug tip
    Also, check if you're not using android.support.v4.app.FragmentTransaction with android.app.Fragment and vice-versa
  6. 0
    samebug tip
    Initialize the variable before calling a method on it.

    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

      monitorEnter called on a null object

      at com.tc.object.bytecode.ManagerImpl.monitorEnter()
    2. com.tc.object
      ManagerUtil.monitorEnterWithContextInfo
      1. com.tc.object.bytecode.ManagerImpl.monitorEnter(ManagerImpl.java:499)
      2. com.tc.object.bytecode.ManagerUtil.monitorEnterWithContextInfo(ManagerUtil.java:496)
      2 frames
    3. anl.cluster.factorial
      RunMaster.main
      1. anl.cluster.factorial.FactorialWork.<init>(FactorialWork.java:12)
      2. anl.cluster.factorial.FactorialMaster.scheduleWork(FactorialMaster.java:137)
      3. anl.cluster.factorial.FactorialMaster.run(FactorialMaster.java:66)
      4. anl.cluster.factorial.RunMaster.main(RunMaster.java:78)
      4 frames