– Badtux the “Open source crap is *still* crap” Penguin
]]>Yeah, it has to be a Javascript loop, and Firefox has not reacted well to them in the past, which is why I have pretty much eliminated all of the Javascript loops that I once ran as widgets on the page.
Another problem may be that it is looking for a cookie, and I am really restrictive on cookies that I accept, and dump them every time I shut down. If it is attempting to write a cookie, it will SOL, although FF normally flags that.
It has to be a combination of scripts, because the problem only exists on Bark Bark Woof Woof, I comment at other Echo/JS-Kit sites with no problems.
There are too many people who write software that doesn’t “play well with others”, and I long for the days when I was a Sys Admin in academia and ruled everything on my network [Unix on a PDP-11].
]]>My guess is that you’re running a leaky old browser and going into a JavaScript loop that’s consuming every byte of memory in the system and throwing it into the Thrash of Death. Unfortunately I can’t tell you to go to Linux to avoid that, because Linux is just as prone to the Thrash of Death as Windows, though the OOM killer *sometimes* manages to eventually kill the browser before the whole system croaks. FreeBSD has much better OOM behavior than Linux or Windows, alas, it also is ridiculously hard to administer and doesn’t have drivers for a lot of modern hardware. So anyhow, what *does* work is going to Google Chrome… when they rewrote the universe from scratch, somehow (I don’t know how) they dealt with the looping and memory leaks and such that JavaScript is prone to. Or JS-Kit could fix their bugs. Good luck on that…
– Badtux the Geeky Penguin
]]>