Having aggregation rows in portlets that use Out of the Box (OOTB) Data providers (Such as Task or Team) causes out of memory issues in environments that have a large amount of data. Symptoms of observed can included the application going down or hanging when the portlet is accessed as the memory reaches it's maximum limit.
Steps to Reproduce: (one example)
This has been identified as: CLRT-74884/CLRT-77376 where all rows are fetched from the database instead of a limited amount of rows.
Resolved in PPM 14.3
Due to the complexity, dependencies and risk, this issue is not feasible to backport a fix to v13.3 or earlier releases. Please see the workaround noted below.
Remove the aggregation row from the portlet.
Below is an excerpt from the Studio Developer's Guide regarding publishing:
You can overwrite list and filter views for users who have personalized views by publishing new views. A user who has not personalized a view sees the changes immediately when you save changes to a view in Studio. A user who has personalized the view does not see changes to the new view until you publish the changes. If you are using partitions, the new published view affects only the partition you select.