Continually updating a AWT component will run out of X resource IDs

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: P4
    • None
    • Affects Version/s: 1.1.2
    • Component/s: client-libs
    • generic
    • solaris_2.5

      If an application continually paints to a component it will eventually
      fail with an error message:

      Xlib: resource ID allocation space exhausted!

      when run under the JDK-1.1.2 for Solaris.

      It would appear the problem is linked to creating and destroying
      Graphics objects on every repaint. Each graphics object probably
      is causing an Xlib GC to be created, and eventually Xlib runs
      out of resource ids.

      This is obviously a X11 / Solaris only problem.

            Assignee:
            Unassigned
            Reporter:
            J. Duke
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: