High eosd memory usage

We've seen eosd killed by OOM killer a few times in recent days:

Jun  6 10:54:23 lxplus022 kernel: Killed process 10935, UID 0, (eosd) total-vm:21141320kB, anon-rss:20615972kB, file-rss:548kB
Jun  5 12:06:41 lxplus029 kernel: Killed process 13132, UID 0, (eosd) total-vm:16738120kB, anon-rss:16242604kB, file-rss:152kB
Jun  1 09:21:00 lxplus076 kernel: Killed process 6409, UID 0, (eosd) total-vm:19334920kB, anon-rss:18384184kB, file-rss:180kB
May 31 12:58:42 lxplus029 kernel: Killed process 25973, UID 0, (eosd) total-vm:20242268kB, anon-rss:11253176kB, file-rss:24kB
May 31 14:25:43 lxplus079 kernel: Killed process 26575, UID 0, (eosd) total-vm:13170548kB, anon-rss:11321296kB, file-rss:300kB
May 29 21:06:15 lxplus084 kernel: Killed process 10009, UID 0, (eosd) total-vm:4046720kB, anon-rss:408280kB, file-rss:124kB

eosd was consuming as much as 20GB of RSS. 

The size of the virtual memory that a process uses is listed as total-vm. Part of it is really mapped into the RAM itself (allocated and used). This is RSS. Part of the RSS is allocated in real memory blocks (other than mapped into a file or device). This is anonymous memory (anon-rss) and there is also RSS memory blocks that are mapped into devices and files (file-rss).