Posts: 5,988
Threads: 755
Joined: Jan 2019
Reputation:
0
WAY too often I get the screen telling me that a script has gone amiss & do I want to kill it or wait.
It happens consistently on Lifehacker.com & the rest of the Gawker sites then it started doing it on Facebook.
Anybody else experiencing this? I'm using Firefox 6.0 at the moment.
Posts: 5,988
Threads: 755
Joined: Jan 2019
Reputation:
0
Make that "practically useless."
A misspelled word in the subject line is SO embarrassing & by the time I caught it, it was too late to edit.
Posts: 19,306
Threads: 1,696
Joined: May 2025
Reputation:
1
Lifehacker opened fully for me in about 3 seconds. I had a couple sites do that a few weeks ago but haven't seen it since.
Chrome ver. 13.0.782.220
Posts: 6,841
Threads: 1,241
Joined: Feb 2012
DaviDC. wrote: A misspelled word in the subject line is SO embarrassing & by the time I caught it, it was too late to edit.
Why? Don't worry about typos.
Posts: 17,354
Threads: 3,275
Joined: Mar 2025
Chrome has been crashing and burning so often the past week. I switched to FF.
Posts: 31,028
Threads: 2,688
Joined: May 2025
chrome also giving me sad face too many days in a row.
Posts: 41,899
Threads: 3,655
Joined: May 2025
Reputation:
5
I've been having all kinds of Firefox problems on every machine.
Often it quits while in the background, unused.
I've just started using Chrome at home and haven't really had much trouble.
Posts: 50,838
Threads: 670
Joined: Mar 2024
freeradical wrote:
Hey, I fixed it!
X(
Does it make more sense now ?
![[Image: 1Tr0bSl.jpeg]](https://i.imgur.com/1Tr0bSl.jpeg)
