*mutter*grumble*

[lethargic_man]

Bah. I let someone at work talk me the other week into changing my Firefox to Deer Park, a build he'd made optimised for my processor... only it didn't work. I wasted a few hours getting that sorted out, then I discovered that file: URLs didn't work, even with the checkloaduri config setting set to false. So I converted all the file: URLs on my homepage to http: ones, as that was considerably quicker than actually tracking down and fixing the problem.

Then, this morning, I discovered that going to livredor's blog had started reproduceably hanging Firefox. This was the last straw; I think I'd had Deer Park hang several times beforehand. So I tried uninstalling Deer Park and reinstalling Firefox. Only the problem still remained. I tried deleting the Deer Park code... only it wouldn't delete, there was an "access violation". Something from the instances that had hung and been killed must not have died properly. I had to reboot my machine to be able to get this to work.

And Firefox still hangs on visiting livredor's blog. You haven't made any changes to your style file, have you, livredor?

So now I'm back using Firefox 1.5, but now have to reconstitute my bookmarks and extensions. Bah, I say. And, to satisfy purists, humbug, too.

---

Update: Firefox just updated itself, and fixed itself. Now that's more like it!

Comments

[doseybat.livejournal.com]

you are not alone. this puter has firefox and it *doesnt* like livredor's blog, often refusing to lead it completely; this has been the case for quite a while. seems ok with any other website though..

[darcydodo]

Yeah, if I'm on anything other than a nice fast connection, livredor's blog really doesn't like to load. And even if it does load, it takes forever even over a nice fast connection. But that's been going on for a long time (as doseybat said).

[lethargic-man.livejournal.com]

That's what I have at home, on narrowband. What I'm talking about here, though, is hanging completely, not simply taking a long time to display: the process needs to be killed and restarted.

[lethargic-man.livejournal.com]

I've managed to recreate the problem with another website. (http://www.wincvs.org/)...