Bug 171218 - REGRESSION(r215088): [GTK] Memory peak on perf test Animation/Balls.html is a 20% higher.
Summary: REGRESSION(r215088): [GTK] Memory peak on perf test Animation/Balls.html is a...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL: https://perf.webkit.org/v3/#/charts?s...
Keywords:
Depends on:
Blocks: 170457
  Show dependency treegraph
 
Reported: 2017-04-24 06:50 PDT by Carlos Alberto Lopez Perez
Modified: 2017-04-24 22:34 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos Alberto Lopez Perez 2017-04-24 06:50:51 PDT
The maximum resident memory on the perf test Animation/Balls.html grew from 119MB to 141MB after r215088 <https://trac.webkit.org/r215088>

At the same time, the JSHeap memory shrinked from 1.12MB to 0Bytes.

https://perf.webkit.org/v3/#/charts?since=1491140313418&paneList=%28%2816-194%29-%2816-92%29%29&repository=1
Comment 1 Zan Dobersek 2017-04-24 11:16:42 PDT
Probably due to the change in priority of the JSRunLoopTimer. It was G_PRIORITY_DEFAULT before (0), now it's been raised to 200, which is the highest value in the RunLooopSourcePriority enum.
Comment 2 Carlos Garcia Campos 2017-04-24 22:34:33 PDT
Just to clarify, highest value which means lowest priority. The idea of that change was to give lower priorities to sources used to releases resource, like garbage collector. The memory pressure has the highest priority because in that case releasing resources is urgent. So, I'm not sure this is a problem.