mswamp wrote:
I have traced this to Mail.app. The trigger seems to be when you drag multiple files into the email to have them included. Then, the memory usage starts racing, eventually using up all free memory within seconds. The only way to recover is to use Force Quit from the Activity Monitor, normal Quit from within Mail does not work. See the attached screenshot. By the time I grabbed the screen shot and pressed Force Quit, it was already up to 17 Gbytes of Memory.
Has anyone else came across this problem?
I didn't bother to read the entire thread. But there are some important plot points here.
First of all, this is most definitely a bug in Mail and perhaps the OS itself. It should never get to 17 GB or 42 GB of memory usage. This is probably dependent on your e-mail ISP and how you have configured Mail. It seems to be getting itself into a loop with draft files that keep cycling back and forth from the server. The best solution would be to turn off internet, launch Mail, delete your drafts, turn internet back on, and keep deleting drafts as fast as you can unit lit settles down. Then quit and relaunch. Maybe it will help, maybe not - just something to try.
There really is no differentiation between "released" and "beta" software from Apple anymore. It's all the same and we are all beta testers, willingly or not. If you want to use Apple software, you have to learn the bugs. If there is something that causes problems for your system, then don't do that. Maybe drag files one at a time. Maybe try to use the menu options or the attach button. The bug may be specific to your ISP so other people may not experience it. That doesn't mean it doesn't exist. I cannot reproduce this particular bug but I can't deny those screenshot. When I attempted to reproduce the problem, I immediately found other obvious bugs.
Considering that we are all beta testers, it is our responsibility to file bug reports. The Apple Bug Reporter is at: https://bugreport.apple.com/. Just don't expect the bug to get fixed. To see a bug fix in a 10.10.1 release, there would literally have to be tens of millions of reports. You should still file the reports, but learn to live with the bugs. The one bug I saw was one I had reported years ago. I am not exaggerating about the tens of millions of reports. There are no magic fixes. You just have to learn the system and don't do the things you know will crash it.
Going along with this, it is important to properly discriminate between different issues. As beta testers we shouldn't confuse them. Having a low level of free RAM is not a bug. That is just the way the OS works. Having hundreds of MB of memory usage for an app is not a bug. That is just normal software bloat. It has to be GB before it is anything worth noticing. If you get the "out of memory" error, that is a problem that should be reported. It should never happen unless you were critically low on disk space. And you should not get critically low on disk space because Mail is taking 42 GB of disk space for swap files. That's a bug.