Make ResolutionErrorEntry's interface less susceptible to memory leaks

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: P4
    • None
    • Affects Version/s: None
    • Component/s: hotspot
    • None

      As discovered by [~iklam], the ResolutionErrorEntry may leak if you're not being careful in how the message strings are allocated.

            Assignee:
            Johan Sjölen
            Reporter:
            Johan Sjölen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: