Comment 16 for bug 658649

There is no disk activity, and physical RAM usage tops out around 1.5 GiB (I have 6 GiB total). Most of it is buffered/cached, with ~300 MiB explicitly labeled "free", and I'm fairly certain that's appropriate for "well designed systems" (quoted from somewhere that seemed legit). Swap has zero usage.

To the end of the linked bug report, would file indexing really cause such a problem? I remember I generally disabled it in the past, but haven't done so this time. Generally, top shows the file I/O processes right below the active processes, but with no active CPU listed.