Latest profile: https://share.firefox.dev/4hgDgYQ It looks like the cleanup doesnt clear a lot of the memory. The testcase uses about 850MB. Despite 3-4 cleanup phases, the memory does not go down. Then i triggered a manual memory cleanup from about:memory, and that took 35 seconds and still the memory uses was about 800MB.
Bug 1935829 Comment 18 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Latest profile: https://share.firefox.dev/4hgDgYQ It looks like the cleanup doesnt clear a lot of the memory. The testcase uses about 850MB. Despite 3-4 cleanup phases, the memory does not go down. Then i triggered a manual memory cleanup from about:memory, and that took 35 seconds and still the memory uses was about 800MB. EDIT: This weird behaviour occurs ONLY with the Gecko profiler enabled. With the profiler disabled, the behaviour is much more on expected lines.
Latest profile: https://share.firefox.dev/4hgDgYQ It looks like the cleanup doesnt clear a lot of the memory. The testcase uses about 850MB. Despite 3-4 cleanup phases, the memory does not go down. Then i triggered a manual memory cleanup from about:memory, and that took 35 seconds and still the memory uses was about 800MB. EDIT: This weird behaviour occurs ONLY with the Gecko profiler enabled. With the profiler disabled, the behaviour is much more on expected lines. Here is a Samply profile that is what you would expect: https://share.firefox.dev/3KQ0fhm
Latest profile: https://share.firefox.dev/4hgDgYQ It looks like the cleanup doesnt clear a lot of the memory. The testcase uses about 850MB. Despite 3-4 cleanup phases, the memory does not go down. Then i triggered a manual memory cleanup from about:memory, and that took 35 seconds and still the memory uses was about 800MB. EDIT: This weird behaviour occurs ONLY with the Gecko profiler enabled. With the profiler disabled, the behaviour is much more on expected lines. Here is a Samply profile that is what you would expect: https://share.firefox.dev/3KQ0fhm
Latest profile: https://share.firefox.dev/4hgDgYQ It looks like the cleanup doesnt clear a lot of the memory. The testcase uses about 850MB. Despite 3-4 cleanup phases, the memory does not go down. Then i triggered a manual memory cleanup from about:memory, and that took 35 seconds and still the memory uses was about 800MB. EDIT: This weird behaviour occurs ONLY with the Gecko profiler enabled. (There have been some recent changes to the way profiler interacts with jit.. maybe thats interferring somehow?) cc iain. With the profiler disabled, the behaviour is much more on expected lines. Here is a Samply profile that is what you would expect: https://share.firefox.dev/3KQ0fhm
Edit: there is some odd behaviour with the profiler and this testcase. I have filed bug 1994907 to track it separately.