I don't have the instance and the steps to reproduce, just the memory dump but here are the info I have in Yourkit.
I tried to find more info and there is indeed something fishy: https://<myhost>/xwiki/bin/get/XWiki/UserDirectoryLivetableResultsOverride?outputSyntax=plain&transprefix=xe.userdirectory.&classname=XWiki.XWikiUsers&collist=_avatar%2Cdoc.name%2Cfirst_name%2Clast_name%2Ccompany%2Cdirection%2Clevel2%2Clevel3%2Clevel4%2Clevel5%2Clevel6%2Cgeosite%2Cphone%2CbusinessUnit%2Cactive%2Cemail%2Caccessibility%2Cmobile%2Cmanager%2Cemployee_type%2Cfunction%2Cskin%2CdisplayHiddenDocuments&queryFilters=currentlanguage%2Chidden&offset=1&limit=3500&reqNo=1&sort=doc.name&dir=asc
NotNo idea how the user ended up with this URL with a limit set to 3500 but that's might be why it's a lot bigger that a 15 rows one.
Will reduce the priority.
Still it's not nice to get a big html in what should ideally return data as fast as possible, the livetable really need some refactoring.
bq. The live table results page builds the JSON and returns it to the live table without keeping any reference
The fact that it's temporary does not really mean you can take as much memory as you want :) When the browser have to download 20M and the thread retain 115M during that time it become a lot less temporary and it spikes very quickly on an active wiki.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
