Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6949515

VM crash when calling GetMethodDeclaringClass

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P3 P3
    • hs19
    • 6u18, 6u20
    • hotspot
    • b09
    • b02
    • x86
    • linux, solaris_nevada, windows_vista
    • Verified

        Invoking GetMethodDeclaringClass with obsolete methodid will crash VM. The bug is originaly reported against NetBeans.
        See <https://netbeans.org/bugzilla/show_bug.cgi?id=183107> for steps how to reproduce it.
        Here are some snippets from the hs_err file from the NetBeans bug link:

        #
        # A fatal error has been detected by the Java Runtime Environment:
        #
        # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d9bd48f, pid=3564, tid=1044
        #
        # JRE version: 6.0_18-b07
        # Java VM: Java HotSpot(TM) Client VM (16.0-b13 mixed mode windows-x86 )
        # Problematic frame:
        # V [jvm.dll+0x10d48f]
        #
        # If you would like to submit a bug report, please visit:
        # http://java.sun.com/webapps/bugreport/crash.jsp
        #

        --------------- T H R E A D ---------------

        Current thread (0x04ada000): JavaThread "*** Profiler Agent Communication Thread" daemon [_thread_in_vm, id=1044, stack(0x04f20000,0x04f70000)]

        siginfo: ExceptionCode=0xc0000005, reading address 0x00000004

        Registers:
        EAX=0x024894f0, EBX=0x00000d90, ECX=0x000071ee, EDX=0x00000000
        ESP=0x04f6fab0, EBP=0x04f6fab4, ESI=0x00000000, EDI=0x02411490
        EIP=0x6d9bd48f, EFLAGS=0x00010206

        Top of Stack: (sp=0x04f6fab0)
        0x04f6fab0: 04ada000 04f6fadc 6d9e230f 024894f0
        0x04f6fac0: 058126e4 024894f0 04ada000 00000000
        0x04f6fad0: 00000000 00000000 04ada000 75eb3e00
        0x04f6fae0: 10002594 02411490 024894f0 04f6fb28
        0x04f6faf0: 04ada000 20152eb0 04f6fb60 20152eb0
        0x04f6fb00: 04c238f8 04c9f5a8 058126e4 00000a65
        0x04f6fb10: 00000000 00000000 05811a38 02509f47
        0x04f6fb20: 04ada110 04f6fb68 04e818f0 04ce1878

        Instructions: (pc=0x6d9bd48f)
        0x6d9bd47f: cc 55 8b ec 8b 45 08 85 c0 75 02 5d c3 56 8b 30
        0x6d9bd48f: 8b 46 04 8d 48 08 8b 01 ff 90 94 00 00 00 f6 d8


        Stack: [0x04f20000,0x04f70000], sp=0x04f6fab0, free space=13e04f6f594k
        Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
        V [jvm.dll+0x10d48f]
        V [jvm.dll+0x13230f]

        Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
        j org.netbeans.lib.profiler.server.system.Stacks.getMethodNamesForJMethodIds(I[I[I)[B+0
        j org.netbeans.lib.profiler.server.ProfilerInterface.getMethodNamesForJMethodIds([I)Lorg/netbeans/lib/profiler/wireprotocol/MethodNamesResponse;+18
        j org.netbeans.lib.profiler.server.ProfilerServer.handleClientCommand(Lorg/netbeans/lib/profiler/wireprotocol/Command;)V+532
        j org.netbeans.lib.profiler.server.ProfilerServer.listenToClient()V+48
        j org.netbeans.lib.profiler.server.ProfilerServer.run()V+22
        v ~StubRoutines::call_stub


        Just to be clear: with product bits, this bug crashes with an
        EXCEPTION_ACCESS_VIOLATION. With debug bits, this bug crashes
        with a nice assertion failure.

        I've attached the complete hs_err file from the NetBeans link
        as hs_err_pid3564.log.

              dcubed Daniel Daugherty
              thurka Tomáš Hůrka
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: