Refactor heap allocation to separate concerns

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P4
    • 11
    • Affects Version/s: None
    • Component/s: hotspot
    • None
    • gc
    • b20

        The current allocation path has object allocation, initialization, tracing, exception handling and sampling all mixed up in a horrible mess.
        It would be nice if these concerns could be better separated.

              Assignee:
              Erik Österlund
              Reporter:
              Erik Österlund
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: