-
Suggestion
-
Resolution: Fixed
-
None
-
None
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.
- details
-
JSWSERVER-417 Add Max in General Configuration persistence
-
- Closed
-
-
JSWSERVER-418 Add Max in TaskBoad Configuration pane - Action/Ajax
-
- Closed
-
-
JSWSERVER-419 Add Action intercepter to handle the Max
-
- Closed
-
- is related to
-
JSWSERVER-431 Look for some ways to reduce the GreenHopper resource consumption.
-
- Closed
-
- relates to
-
JSWSERVER-409 Need the ability to hide Task Board and Planning Board links from anonymous users (well, spiders in particular)
- Closed