I found another ticket which points to exactly the same issue occurring in the past:
However, it seemed that was resolved as part of this ticket: Loading...
Are there any other known memory leaks to look out for? Could it be due to some interaction between the projector and the memcached process (since this only started happening after enabling indexing)?