http://glui.me/?i=uu1gqb3son0sbnn/2015-08-11_at_11.33_AM.png...
You can see where the memory sets itself during the rethink process restart, and then it slowly climbs back up to ~3gb, despite no new data being written to the system (all our RethinkDB data is generated during deploy time).
Any pointers? I'd be happy to provide any diagnostics.
The image doesn't seem to load for me. Would you mind opening a GitHub issue (https://github.com/rethinkdb/rethinkdb/issues/new) with as many details as possible? We need to know a bit more about the infrastructure/workload to replicate this; once we get the info we'll get to the bottom of it ASAP.
Also feel free to e-mail me at slava@rethinkdb.com if you need urgent/critical support.
It helps if you include information on your setup in the issue (for a list of helpful details, read "How to submit a bug report" here: http://rethinkdb.com/docs/crashes/).