You will need direct database access to do this test. NOTE: This test reproduces the problem with a single large log, because that's easier to set up, but the problem actually appears with multiple smaller logs that add up to a lot. NOTE: The SQL REPEAT function used here works on Postgres and, allegedly, on MySQL. Go to the task logs page on your test server's site administration ( Server / Tasks / Task logs ). Hopefully you have at least 2 pages of task logs. If you don't, run cron a few times. Go to page 2 of the list. Select one of the tasks at random. Mouse over the magnifier icon - your browser should show a URL such as /admin/tasklogs.php?logid=621 . Make a note of the number (621 here). In your database, run the following query, replacing the number 621 with the correct one and the PREFIX with your database table prefix. This is intended to set the output field for this log task to about 150MB of data. Postgres: update PREFIX_task_log set output=REPEAT(E'I am a large log file 32 bytes.\n', 5000000) where id=621 MySQL: update PREFIX_task_log set output=REPEAT('I am a large log file 32 bytes.\n', 5000000) where id=621 (maybe) Reload the task log page. EXPECTED: It should re-display, looking the same as before (and not, for example, crash with a memory error). Click the magnifier icon next to the log you changed. EXPECTED: The very large log file should display in the browser window (and not give a memory error). Note: There is still a limit on the size of log files displaying, but hopefully not now on the table display.