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

IMFSPI:Exit Kana-kanji Conversion window causes VM abort on Passive Client

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not an Issue
    • Icon: P4 P4
    • None
    • 1.4.1
    • client-libs



      Tested OS : RedHatLinux 7.1/7.2
      Winow manager : Gnome
      Reproducible test cases : SPI403/404
      Reproducible jdk version : hopper fcs, hopper-rc, Merlin FCS


      To reproduce,

      1. Assign IM selection key.
      2. Run SPI403 or 404 test case.
      3. Select Host IM.
      4. Press shift + space to activate Japanese input mode.
      Then, Kana-kanji Conversion window appears.
      5. Exit Kana-kanji Conversion window pressing X located at the right top corenr.
      Then, the test application abnormally ends with error messages:
      Or
      sometimes all opened windows dissappears: not only the spi test case's windows, but also the terminal window on which the command for the SPI test case is executed disappers.
      =========================================================================
      An unexpected exception has been detected in native code outside the VM.
      Unexpected Signal : 11 occurred at PC=0x82368E3
      Function=[Unknown.]
      Library=(N/A)

      NOTE: We are unable to locate the function name symbol for the error
            just occurred. Please refer to release documentation for possible
            reason and solutions.
      ..........
      =========================================================================
      The error log was saved(attached as hs_err_pid1942.log.

      At this point kinput2 is defunct:
      > ps -elf | grep kinput2
      004 Z tokunaga 1175 1111 0 69 0 - 0 do_exi 18:05 ? 00:00:00 [kinput2 <defunct>]


      Trying this test with some previous version of jdk(hopper-rc and Merlin FCS), this is reproducible, so this is not a regression.

      This causes java VM aborting and make hostIM defunct, so this seems a severe problem, however, following the instruction of the test cases or pressing shift + space to deactivate Japanese input mode this problem is not seen. I think that it can be a workaround and it is not a showstopper for Hopper FCS at this critical time.

      * This kind of problem was seen with other operation also, however, trying many times, I could not specify the reprodubible steps.
      I'll continue the investication and I'll update the report when I can specify the steps.





            naoto Naoto Sato
            mtokunagsunw Miki Tokunaga (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: