I have been seeing this happen frequently.  After my 8gb of memory slowly fill up my emhttp crashes, when I try to start it again I get a segmentation fault.  Only way of getting it back up is restarting the unRAID server.  I even stopped ALL the services and it seemed like the memory would not flush.  Is there a solution to this?

 

Version 5.0b14

 

Running Plex, AirVideo, SabNZBd, SickBeard, CouchPotato, Transmission and unmenu.  I have Plex running on my /mnt/cache/custom folder (without a . in the name due to memory leak)

 

 

Here is TOP after 8 hours:

 

(from /usr/bin/top -b -n1)
top - 17:17:42 up 18:12,  0 users,  load average: 1.89, 2.15, 2.00
Tasks:  92 total,   1 running,  91 sleeping,   0 stopped,   0 zombie
Cpu(s):  1.0%us,  6.1%sy,  0.1%ni, 89.2%id,  0.8%wa,  0.0%hi,  2.9%si,  0.0%st
Mem:   8050132k total,  5890680k used,  2159452k free,    79180k buffers
Swap:        0k total,        0k used,        0k free,  5258752k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND            
7155 nobody    20   0  212m  25m 3420 S    4  0.3   5:10.31 python             
11941 nobody    20   0  194m  21m 3228 S    2  0.3   1:04.51 python             
    1 root      20   0   828  304  264 S    0  0.0   0:02.25 init               
    2 root      20   0     0    0    0 S    0  0.0   0:00.00 kthreadd           
    3 root      20   0     0    0    0 S    0  0.0   0:02.63 ksoftirqd/0        
...
...
...

I even stopped ALL the services and it seemed like the memory would not flush.  Is there a solution to this?

reboot

Here is what solved it for me:

 

I moved my Plex out of a folder with a dot (.) in front of it, my cache drive folder .custom is now custom (without the dot) and I unshared it, not visible now and added it to the ignore list of the mover script, all working fine now.