Details
Description
I have used Qt Demo Browser with EGLFS on the platform and opened a particular web server which features JavaScript codes. I leave it soak running that web application. The page's script clearly does something periodically even when there is no interactions with the page. I monitor QtWebEngineProcess which has launched a renderer process at the moment and sees the renderer keeps allocating memory without freeing it up. There seems to be a saturation point at which QtWebEngineProcess will stop allocating further memory but it never frees up that memory forward that point.
It's in contrast with the behavior of QtWebEngineProcess 5.6 on Windows towards the same web page. On Windows, the memory occupied by QtWebEngineProcess is highly stable.
I have also tested opening the same web page using Chrome Version 54.0.2840.100 on Linux (exactly the same platform as I used for testing Qt Demo Browser) and noticed Chrome also manages that memory very well and can avoid accumulating unused memory.
The importance of this poor memory management is that QtWebEngineProcess might get killed by the Linux OOM (out of memory) killer during the time it's occupying more and more memory and before it reaches the saturation point.