hat
  1. hat
  2. HAT-4

Unable to parse binary hprof due to Thread 2000x not found

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: current
    • Fix Version/s: milestone 1
    • Component/s: www
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      4

      Description

      When feeding HAT with a binary hprof file I always get the following stacktrace
      (depending on de JVM version the thread number may differ):

      Started HTTP server on port 7000
      Reading from .\dump.hprof...
      Dump file created Sun Jan 25 06:35:09 CET 1970
      java.io.IOException: Thread 200009 not found for JNI local ref
      at hat.parser.HprofReader.getThreadObjectFromSequence(HprofReader.java:577)
      at hat.parser.HprofReader.readHeapDump(HprofReader.java:365)
      at hat.parser.HprofReader.read(HprofReader.java:221)
      at hat.parser.Reader.readFile(Reader.java:90)
      at hat.Main.main(Main.java:149)

      I'm aware that various bugs with similar stacktraces have been closed in the
      JDC, but the above stack trace is based on the JVMs belows, so it appears that
      these bugs are not fixed or that there is some other bug in HAT.

      java version "1.5.0_04"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
      Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)

      java version "1.6.0-ea"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-ea-b42)
      Java HotSpot(TM) Client VM (build 1.6.0-ea-b42, mixed mode)

      I encounter the same problem on Solaris 8 x86 as well as for Windows XP.

      I admit that the last year I tried to run HAT against various versions of J2SE
      1.5 and never have I been able to get it running, so up till now I'm rather
      disappointed by the experience so far. And that is a shame for I really need a
      tool like HAT for finding complex memory leaks that require a full heap
      analysis, the other commercial tools are nice for 'simple' memory leaks but for
      some reason they all fail in the area where you are looking for that one root.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            hat-issues
            Reporter:
            marbro
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: