JNI Weak Ref handling needs improvement

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P2
    • 1.3.1_04
    • Affects Version/s: 1.4.0
    • Component/s: hotspot
    • None
    • 04
    • generic
    • generic


        See bug 4462056 regarding JNI Specification problems with weak refs.

        It is currently possible to pass a deleted weak reference as an
        argument, resulting in the access of a private object internal to
        hotspot (call a sentinel). A more appropriate action is desirable,
        including a fatal error.

        Passing weak refs to most JNI functions should be illegal, and in any
        case, is a bad idea. See comments.


              Assignee:
              Fred Oliver (Inactive)
              Reporter:
              Fred Oliver (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: