Home › Forums › Open Discussion › Does anyone else have problems viewing WSB comments via Firefox?
- This topic has 8 replies, 6 voices, and was last updated 7 years, 12 months ago by zephyr.
-
AuthorPosts
-
September 29, 2016 at 8:40 am #859319
zephyrParticipantFor quite some time now, I have been having problems viewing comments on the WSB via Mozilla Firefox browser. Some days I can quickly take a look and get out of the comments. But most days after being in the comments–particularly the topics with more comments, something happens. I notice that scrolling down gets “jumpy”, then suddenly my browser freezes. Sometimes, I can start exiting the Blog and shut down Firefox. But often even after closing the WSB browser window and the tab with comments, my other Firefox windows that are open in the background start to freeze. Then at that point it becomes difficult to shut down FF and my computer locks up. I have to force a restart.
I view a number of blogs and sites using Firefox through the course of the day, but this only seems to occur with the West Seattle Blog. Does anyone else notice this problem? I am writing this post from Internet Explorer. I prefer using Mozilla, but use IE as a back up occasionally. (Note: I am on a PC using Windows 7.) Thanks, ~z
.September 29, 2016 at 9:07 am #859323
squareeyesParticipantWindows 10 Enterprise here using Firefox 46; no problems viewing for me.
September 29, 2016 at 9:49 am #859326
mpentoParticipantI get that sometimes at work not at home. Firefox on both computers. It is just the crappy connection at work. When it gets busy get data traffic jam. I think it might have something to do with ads loading. But I did not stay at a holiday in last night
September 29, 2016 at 12:43 pm #859361
ChemistParticipantI have a lower-power Win 7 x64 laptop that tends to have Firefox crash after loading up WSB. It usually takes a while to become unresponsive, but eventually the tabs stop responding quickly and I can see one of 4 CPUs will stay pegged such that the resource monitor remains above 25%. I figured there’s some ad script that stays running until memory usage gets out of control. On that laptop, I try to remember to fire up Chrome before going to WSB.
I have a more powerful desktop that’s also running Win 7 and Firefox and don’t see this problem on it. Not sure why.
September 29, 2016 at 2:26 pm #859383
zephyrParticipantWell I also play internet radio on iTunes at the same time. Recently a friend told me that iTunes runs extra programs in the background and uses up resources (I can’t explain it technically.) So I wonder if that is an issue as well. It’s just odd. The WSB is the only site that have this issue with so far. Maybe it is resource heavy. I appreciate all the comments thus far. ~z
.September 29, 2016 at 3:31 pm #859391
Michael WaldoParticipantI use Win 7 with Firefox. I have noticed the blog is loading way slower the last few months than it used to. I think it has to do with all the fancy features added in the upgrade. There is a lot of data to download on the main page. I have 50MB broadband download speed, so it can’t be to connection. It is a bit annoying but I have learned to deal with it.
September 29, 2016 at 6:17 pm #859413
zephyrParticipantSlow loading I can handle. It’s the completely freezing up and turning the page to blank that’s a pain. And it’s hard to get out of it. I try to shut the pages down when this happens, but often hard to even resort to Ctl_Alt_Del to get the Task Manager going. Even then it can hang up and not let me re-start. For some reason, Firefox and WSB don’t work well together. I was hoping to hear that this was happening to other FF users. Maybe someone has figured this problem out already. Right now I am on IE to write this post.
September 29, 2016 at 10:00 pm #859441
justadumbguyParticipantYes, this happens frequently to me as well using FF and win7 FF becomes unresponsive and CPU gets locked at 25%.
September 30, 2016 at 9:17 pm #859571
zephyrParticipantGreat. There’s at least two of us. There may be others.
-
AuthorPosts
- You must be logged in to reply to this topic.