![]() ![]() The questions here are (a) does this fix your problems and (b) does the maintenance that gives you feedback (disk repair, permissions) show the same errors coming up again after a short enough time (a week, two weeks). Running all the mentioned general maintenance (Disk repair aka fsck, permissions, cleaning system caches aka Onyx & Co.) is the next step. If other caches are the vector, this is harder to find (though if the problems are concentrated on one application, caches used by this application are the first thing to look at). Smaller ones, particularly if distributed over multiple processes are harder to find but should eventually be identifiable. ![]() Large memory leaks are usually easy to find because the offending application or process uses so much RAM that it sticks out. Or you could have memory leaks, ie, one or more application and processes keeps increasing its RAM footprint. You can run out of RAM simply because you want to do more at the same time than you have RAM for (solution get more RAM). ![]() If RAM is one of the vectors, you can easily check this via Activity Monitor, ie, if your free RAM is very low and you have swap outs and disk activity during those beachball moments, then you have a winner. What a restart resets is foremost RAM and a number of other caches. If a restart fixes it temporarily, one element in the cause-effect chain of your problem must be something that gets cleared or reset during a restart, but the root cause itself is somewhere else. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |