[opensuse] Going nuts now...
Recent install of 10.2, all updates are current, so far as I know. Within the past couple of days, Firefox has been going nuts...and taking me with it. When I enter a site to go there, the status bar at the bottom of the browser shows progress, fairly quick (I am on a cable), then shows "Done" on the left, and the site on the right...but the screen has not changed, and may not change for several minutes, real clock minutes, not just a "long time". This can sometimes happen just clicking on a link within a site. Sometimes I may just go to another tab to do some other browsing, and when I return, lo and behold there is the site. As I have long suspected with computers this seems to be approaching the realm of magic now. Using AMD _64, 10.2 from downloaded DVD, all updates suggested by the updater. No other real problems so far, well, the sound does not seem to work but that has not been so critical to me at the moment other than amorak and kaffeine will not work without it: Yast says it is fine and even plays the test sound so it is not completely kaput. Will not recognize any mixer yet. Will mess with that when it becomes more of a nuisance. The browsing thing though is getting me down. CPU load seems awfully high, and most of the time. Are these maybe related? Sometimes shows up to 50% according to graphical Ksysguard monitor in system tray. When I go into a terminal and enter "top" to see whats up, it drops back to nearly nothing usage. Confused. Anyone else seeing anything like this? I know there was a thread maybe yesterday or so about high CPU usage but did not mention browser "slowness" with it. Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
The browsing thing though is getting me down. CPU load seems awfully high, I have seen this behaviour in Mozilla suite and Seamonkey, with sites
On 2006-12-19 14:48, Richard wrote: that rely heavily on javascript, particularly one site that uses it (amongst other things) to perform periodic auto-refreshes. Usually, though, things are OK for awhile; the CPU load goes through the roof after several refreshes. There is also a memory leakage that occurs on the same site. Sooner or later, a memory corruption will occur, after which nothing works -- email, browser, everything sits there looking like it is functioning, but nothing works at all. Some time ago (I cannot recall when or where), I found a reference online suggesting that this behaviour was due to a failure of the web page to deallocate existing javascript functions before allocating them again, or something like that (the memory corruption is, of course, something quite different). Now, I don't bother keeping that site loaded all the time, and the browser behaves quite well. If this is the same problem you are having, AFAICT, it is not something which can be resolved within the browser -- it is rather a failure of the website maintainers to write robust javascripting. -- The best way to accelerate a computer running Windows is at 9.81 m/s² -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Darryl Gregorash
-
Richard