: K-Meleon Forum
General discussion about K-Meleon.
[quote=Terry] Thank you foobarly; you are being extraordinarily patient in answering my questions. Both Process Explorer and Taskmanager are tools. For example, if you have taskmanager up and minimize K-M, the memory usage should drop radically. As you let K-M just sit there with no activity, the memory usage should then build to anywhere from a quarter to half of what it displayed during full usage. With Process Explorer with the bottom panel displayed, you can watch how processes are invoked for a certain page in K-M and then how such processes reach an endpoint, meaning that their memory is surrendered back to the system since they are no longer needed. When a process does not display an endpoint (process colored red if you go by the default coloring scheme), this is a memory leak. It seems to me that Dorian uses a lot of Windows native modules to accomplish what K-M does and by-passes the Mozilla functions that can do the same thing. It seems to me, he has done an admirable job with the Windows modules, so comparisons to Firefox are not always pertinent. It is entirely up to you, but I suspect that one of your extensions may be where the problem lays. You could watch for the memory usage actively under Process Explorer to see if a process does reach an endpoint and surrender its memory or if it duplicates it and retains memory. Or, you could discontinue one extension at a time to see how your memory usage responds. Then, there is always the problem of background processes that may be intercepting K-M's tcip strings and holding them for their own purposes making K-M look like the culprit.[/quote]
K-Meleon forum is powered by