Several times, when I want to see a site, and notice that it will take to much time, I order for the computer to stop. I click on the X with the mouse and I press Esc in the keyboard, but generally the computer don't obey, or it take very much time until the computer stop. Is it so difficult to create a navigator that obeys more to the order that come form the keyboard (the orders of the owner) than to orders of externals sources? Is it so difficult? I think that is a bias form the guys that create the navigators. When I cut the electricity, the computer ever knows how to stop.

Your problem doesn't seem to be one native to K-Meleon, but rather to computer maintenance and RAM. Here are a few links:

http://miekiemoes.blogspot.com/2008/02/help-my-computer-is-slow.html
http://www.bleepingcomputer.com/forums/topic44694.html
http://www.malwareremoval.com/tutorials/runningslowly.php

Sometimes, especially with KM 1.6 beta, I have that prob too, the whole browser window seems like frozen for a long while. But have lately noticed that it helps to keep a second browser window open (can stay empty), and if one window 'freezes', I click the other one in the taskbar, that seems to break up the queue: immediately the first window is reacting again to the mouse and keyboard :cool:



Edited 1 time(s). Last edit at 01/16/2011 08:01PM by siria.

In fact, you can click any type of other window and back to KM to wake it up. I am fairly certain this is a KernelX problem, maybe related to using KernelX for some programs but not all of them, creating multiple queues for moouse and keyboard events. I will try to research it a little more this week.

Any XP users experiencing these lockups? Sometimes they never time out.

Also, it looks like Flash running can prevent clicks from getting through to the browser.