3 ms·
Next time it happens, can you try running heap(1) against it? It might help point out where that memory is going.
by saagarjha 5y ago
Next time it happens, can you try running heap(1) against it? It might help point out where that memory is going.
- alin23 5y agoJust happened again [0] and no amount of app killing helps. I ran heap(1) on WindowServer [1] but there's nothing in there standing out so maybe this is a red herring. [0] https://cln.sh/A7YPLN https://cln.sh/A7YPLN [1] https://gist.github.com/772687dba65a35cca8cd707fcfda99c0 https://gist.github.com/772687dba65a35cca8cd707fcfda99c0
- saagarjha 5y agoNot a red herring, just confirming it wasn't a normal application memory leak (it's not, the malloc usage is fine–I think you're hitting the same issue as is mentioned in this article). The next step I would do is run sudo footprint $(pgrep WindowServer), optionally with -v to give you a really detailed list of why the footprint is so high.
- deleted 5y ago[deleted]