If objects (like tasks) accumulate a huge number of transactions (say, many thousands), we'll load and display all the transactions. Although this is is very rare under normal circumstances, some types of long-lived objects (configuration? repositories?) will probably tend to accumulate a huge number of transactions over time, and automated scripts can produce a large number of transactions quickly.
Instead, we should show the most recent 500, and then let the user click somewhere to load more in chunks of 500 or something.