Configurable Heap Profiler Maximums

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Diagnostics
    • None
    • Storage Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the heap profiler will stop collecting information once it hits a hardcoded maximum. Messages like the following will be printed out once in the logs:

      too many stacks; disabling heap profiling
      too many live objects; disabling heap profiling
      

      For situations where more data collection is necessary, it would be useful to set a different maximum so these limits don't get hit.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Danny Hatcher (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: