Facebook issues iv'e noticed.
Hi Chris long time user and very thankful for your work keeping my PPC mac relevant. I have noticed while typing in the input box in facebook on my page or commenting on others posts sometimes when typing the thing freaks out and what I can assume is its thinking I'm pressing keybord shortcuts scrolls down to the bottom of the page while typing and I'm forced to hit the home key or scroll back to the top of my page or friends page and start typing again. Also lots of spinning beach ball memory access facebooks updated code any ideas?
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Chris (chtrusch... on 03 Oct, 2016 09:08 AM
Hi, I've never seen this particular behavior while typing on Facebook. No idea what could cause this for you. Have you tried it with all add-ons disabled?
Spinning beachballs on websites depend on your system specs. FB is quite a challenge to any browser. What's your processor type/speed and memory installed?
2 Posted by Brian Szemon on 04 Oct, 2016 02:18 AM
It's a mac mini 1.42 GHz G4 (7450) with the max ram of 1GB DDR SDRAM.
I figured out the glitch with the typing I have to set the cursor in the box and wait a few seconds for things to load I traced it back to a plugin called FBP "Facebook Purity" it changes the code around to get rid of annoyances but call times are longer on this old box. With that plugin disabled page load times are faster and the glitch dose not happen so I will have to live with this if I want to continue using it. Also dose prefetching and network.http.pipelineing increase memory usage when enabled in about:config? got both set low maxrequests and max-optimistic-requests set to 2. Seems to make pages load faster when these are enabled.
Support Staff 3 Posted by Cameron Kaiser on 04 Oct, 2016 02:28 AM
I would strongly recommend against prefetching. What happens in that case is that the browser will try to guess where you'll go next and have those resources ready. On a multiple CPU machine this might pay off if it guesses right (it doesn't always), but on a single CPU like your mini you will spend additional time grabbing those files and trying to handle them at the same time the browser is trying to handle the page you're currently looking at. It will certainly increase memory usage trying to get those files speculatively, and it will probably make things slower overall.
As far as pipelining, you can try it and for many sites it does improve things, but for other sites it's a wash and a few sites will not work properly, which is why it is not the default.
4 Posted by Brian Szemon on 04 Oct, 2016 02:36 AM
Thanks Cameron I've disabled prefetching but will still continue to experiment with the pipelineing the default numbers were too high and why i settled on setting both to 2.