Maybe you can debug a little if you see that happen again?
Perhaps something like this to get the largest number of instances, if
there is a per-file leak:
IN: scratchpad all-instances [ class-of ] histogram-by
sort-values reverse 10 head .
Some other words for
Yes, I could find out a bit more about the memory issue.
I tried it again this afternoon. After 50 minutes into the action
0 "path" t [ link-info ... ] each-file
the system 'top' shows RES rises above 1.2GB and %MEM becomes 15.7%
and they continue to rise.
It blacks out the gui window of
You can run your code in the leaks combinator and it will show you what
leaked. I suspect that you're just using a lot of memory though.
[ { 1 2 3 } [ malloc drop ] each ] leaks members .
{ ~malloc-ptr~ ~malloc-ptr~ ~malloc-ptr~ }
On Thu, Oct 1, 2015 at 12:31 PM, HP wei