• We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      The StepBoard contained in the request maintains a List of Issue objects (the result of a search, so DocumentIssueImpl instances in practice). This list can get very large if the issues happen to contain any large fields such as environment or description. On http://jira.atlassian.com we have seen OutOfMemoryError heap dumps that have contained 300MB of StepBoard instance retained memory - and 600MB of Document instance retained memory (which is mostly stack-local, we haven't worked out what stack frames own this yet).

      As we are not familiar with the code, we aren't sure why this is implemented in this way, but it is a potentially unbound resource use that does not scale well at all. Please consider limiting the results via a PagerFilter.

            [JSWSERVER-406] High memory usage of request local StepBoard

            No work has yet been logged on this issue.

              Unassigned Unassigned
              jwesleysmith Jed Wesley-Smith
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: