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

rundll32.exe application hang with 100% CPU during uninstall of JRE 7u55 i586

XMLWordPrintable

    • x86_64
    • windows_7

      FULL PRODUCT VERSION :
      Java 7 Update 55

      ADDITIONAL OS VERSION INFORMATION :
      Windows 7 Enterprise x64 ( Microsoft Windows [Version 6.1.7601] )

      A DESCRIPTION OF THE PROBLEM :
      Normally I deploy new JRE updates by running a silent install of the exe files as part of a startup script. I let the exe install over the previous version of Java. Normally I install both x64 and i586 versions on our x64 OS's.

      The last known good installer I've been able to deploy without issue is 7u51.

      After attempting to deploy 7u55 on my systems, I noticed the x64 version was installing fine but the i586 was not getting installed. I finally did get it installed, not sure how, but as part of my troubleshooting I attempted to uninstall Java and then try a clean install.

      Based on my experience, my theory is this: on a 64 bit Windows 7 OS, there is a nasty problem when trying to uninstall the i586 version of JRE 7u55. I believe this is related to/regression of the "double slash" problem found in previous MSI files, wherein the UninstallJRE custom action contained an extra slash in the path to installer.dll. I say this because when I try to perform a repair install using msiexec /fvaum, I get prompted with:

      There was a problem starting C":\Program Files (x86)\Java\Jre7\bin\\installer.dll" The specified module could not be found.

      The problem I am reporting is an application hang coming from rundll32 (which is trying to run installer.dll) when trying to uninstall the i586 version of JRE 7u55. The process never finishes, and the CPU is pegged on rundll32 *32.

      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      1. Install JRE 7u55 i586 on Windows 7 64 Bit
      2. Install JRE 7u55 x64 on Windows 7 64 Bit
      3. Attempt uninstall, either msiexec /x or via "Programs and Features"


      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      uninstall should have completed.
      ACTUAL -
      rundll32 process got hung. I terminated the process which allowed the uninstall to complete.

      ERROR MESSAGES/STACK TRACES THAT OCCUR :
      I have run adplus in hang mode on rundll32 and created a dump file. it seems I cannot upload the dump file here but here is the exception analysis as provided by WinDbg. the analysis seems to implicate deploy.dll

      *******************************************************************************
      * *
      * Exception Analysis *
      * *
      *******************************************************************************


      FAULTING_IP:
      +0
      00000000 ?? ???

      EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
      ExceptionAddress: 00000000
         ExceptionCode: 80000007 (Wake debugger)
        ExceptionFlags: 00000000
      NumberParameters: 0

      CONTEXT: 00000000 -- (.cxr 0x0;r)
      eax=00000000 ebx=0017d54c ecx=00000000 edx=00000000 esi=0017d4d0 edi=00000000
      eip=77c3102a esp=0017d410 ebp=0017d4a0 iopl=0 nv up ei pl zr na pe nc
      cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246
      ntdll!NtOpenKeyEx+0x12:
      77c3102a 83c404 add esp,4

      BUGCHECK_STR: 80000007

      DEFAULT_BUCKET_ID: APPLICATION_HANG

      PROCESS_NAME: rundll32.exe

      ERROR_CODE: (NTSTATUS) 0x80000007 - {Kernel Debugger Awakened} the system debugger was awakened by an interrupt.

      EXCEPTION_CODE: (HRESULT) 0x80000007 (2147483655) - Operation aborted

      NTGLOBALFLAG: 0

      APPLICATION_VERIFIER_FLAGS: 0

      APP: rundll32.exe

      ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre

      DERIVED_WAIT_CHAIN:

      Dl Eid Cid WaitType
      -- --- ------- --------------------------
         0 12c8.b0c Speculated (Triage)

      WAIT_CHAIN_COMMAND: ~0s;k;;

      BLOCKING_THREAD: 00000b0c

      PRIMARY_PROBLEM_CLASS: APPLICATION_HANG

      LAST_CONTROL_TRANSFER: from 77112261 to 77c3102a

      FAULTING_THREAD: 00000000

      STACK_TEXT:
      0017d410 77112261 0017d54c 0002001f 0017d460 ntdll!NtOpenKeyEx+0x12
      0017d4a0 77112406 00000154 0017d4d0 00000000 kernel32!LocalBaseRegOpenKey+0x10c
      0017d508 771122f2 00000154 0017d7a4 00000000 kernel32!RegOpenKeyExInternalW+0x130
      0017d528 72cf2ef5 00000154 0017d7a4 00000000 kernel32!RegOpenKeyExW+0x21
      WARNING: Stack unwind information not available. Following frames may be wrong.
      0017d54c 72cf38e9 00000154 0017d7a4 0002001f deploy!Java_com_sun_deploy_security_WinDeployNTLMAuthCallback_IsTrustedSite+0x535
      00000000 00000000 00000000 00000000 00000000 deploy!Java_com_sun_deploy_security_WinDeployNTLMAuthCallback_IsTrustedSite+0xf29


      FOLLOWUP_IP:
      deploy!Java_com_sun_deploy_security_WinDeployNTLMAuthCallback_IsTrustedSite+535
      72cf2ef5 85c0 test eax,eax

      SYMBOL_STACK_INDEX: 4

      SYMBOL_NAME: deploy!Java_com_sun_deploy_security_WinDeployNTLMAuthCallback_IsTrustedSite+535

      FOLLOWUP_NAME: MachineOwner

      MODULE_NAME: deploy

      IMAGE_NAME: deploy.dll

      DEBUG_FLR_IMAGE_TIMESTAMP: 5327d21b

      STACK_COMMAND: ~0s ; kb

      BUCKET_ID: 80000007_deploy!Java_com_sun_deploy_security_WinDeployNTLMAuthCallback_IsTrustedSite+535

      FAILURE_BUCKET_ID: APPLICATION_HANG_80000007_deploy.dll!Java_com_sun_deploy_security_WinDeployNTLMAuthCallback_IsTrustedSite

      ANALYSIS_SOURCE: UM

      FAILURE_ID_HASH_STRING: um:application_hang_80000007_deploy.dll!java_com_sun_deploy_security_windeployntlmauthcallback_istrustedsite

      FAILURE_ID_HASH: {f70653d7-cb12-f60b-9901-42d37f68c325}

      Followup: MachineOwner
      ---------


      REPRODUCIBILITY :
      This bug can be reproduced often.

      CUSTOMER SUBMITTED WORKAROUND :
      None so far

            dmalav Dinesh Malav (Inactive)
            webbuggrp Webbug Group
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: