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

JCK15fcs JEditorPaneTests0003 messes up intermittently due to apparent Swing problem

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: P3 P3
    • None
    • 5.0
    • client-libs

      There is one test that fails (messes up) when it is run with Java HotSpot.

      The interactive JEditorPaneTests, more specifically
      /JEditorPaneTests0003/, is a test that displays a link and a table.
      See attached screenshots. It loads two HTML pages that link to one and
      another, and the test allows the user to click from one page to the
      other back and forth.

      Sometimes when you follow the links "Next Page" and "Previous Page", the
      Simple Table is not formatted correctly, see attached screenshot. I have
      here marked the failing formatting with a red line. When this happens,
      if you move the mouse pointer over the area with wrong formatting, a
      number of java.lang.NullPointerExceptions are thrown.

      This occurs when the test is run with HotSpot (build 1.5.0-b64, mixed
      mode). However, it happens only about every 20th time or so, of clicking
      back and forth between the pages. So this is a bit difficult to reproduce.

      *Test details:*
      **
      *Test:* api/javax_swing/interactive/JEditorPaneTests.html#JEditorPane
      /JEditorPaneTests0003/
      **
      *Problem:* the HTML is sometimes not formatted correctly and moving the
      mouse pointer over a table with wrong formatting will make the test
      throw a long list of java.lang.NullPointerExceptions.
      **
      *Occurs on: *Windows 2000/2003 ia32 and RHEL 3.0 ia32 and ia64. Probably
      other Linux platforms as well.

      My guess is that there is something broken when the HTML is loaded
      into the panel, which could be interesting for you to look into.
      If there is any more details that would be of value for you, please
      let me know.

      --

      NOTE:
      Bug 5087208 reports loosely similar symptoms. This bug has been fixed
      in Mustang_b11. The root cause seems different, though, because the
      problem reported in the present bug report at hand was observed again
      when tested against Mustang_b11 and Mustang_b12.

            idk Igor Kushnirskiy (Inactive)
            clucasius Carlos Lucasius (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: