In file manager, if I click into a directory that contains a metric boatload of files (798,351), file manager stews for a while then pops a pink “Proxy Error” box at the top of the screen. However, the ruby process on the ood server continues to run and suck up memory doing an lstat() on every file in that monster directory, eventually getting OOM killed when it gets too big (around 10GiB on my OOD Server). It seems like the “Proxy Error” should kill the ruby process, and/or a config file limit should be added so that the file manager knows to give up after some number of files.
Thanks for alerting us to this Ric! Scaling issues like these can be difficult to catch before they pop up in the wild, and adding a limit to how many files the file manager will attempt to take on is a good suggestion to handle some of these unwieldy directories more cleanly. I have opened Files app continues large file read after error · Issue #4856 · OSC/ondemand · GitHub to fix this.