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

java.io.PipedInputStream spins CPU, IOException constructor hung

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: P4 P4
    • None
    • 1.1
    • core-libs
    • None
    • generic
    • generic

      Using multiple PipedInputStream/PipedOutputStream paris in multiple
      threads, the system will get wedged in java.io.PipedInputStream.receive(PipedInputStream.java). It spins the
      CPU, with the active thread going between the thread doing the
      write, and the clock thread. It seems to be in the P12 clock
      thread pretty often (see attached thread dumps).

      It's pretty easy to recreate:
          - run ~billf/bin/demo
          - Ask for the project index (wait a few seconds for object serialization
            to happen)
          - Click on the "entire class hierarchy" link
          - Scroll down to the entry for Type
          - Move the window to the right side of the screen, so that the windows
            you're about to create won't cover the current window
          - Click on the <members> tag for every type listed under Type

      This starts up multiple threads, each with a reader/writer pair.

            zlisunw Zhenghua Li (Inactive)
            bfootesunw Bill Foote (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: