Firefox
The latest news and developments on Firefox and Mozilla, a global non-profit that strives to promote openness, innovation and opportunity on the web.
You can subscribe to this community from any Kbin or Lemmy instance:
Related
- Firefox Customs: [email protected]
- Thunderbird: [email protected]
Rules
While we are not an official Mozilla community, we have adopted the Mozilla Community Participation Guidelines as far as it can be applied to a bin.
Rules
-
Always be civil and respectful
Don't be toxic, hostile, or a troll, especially towards Mozilla employees. This includes gratuitous use of profanity. -
Don't be a bigot
No form of bigotry will be tolerated. -
Don't post security compromising suggestions
If you do, include an obvious and clear warning. -
Don't post conspiracy theories
Especially ones about nefarious intentions or funding. If you're concerned: Ask. Please don’t fuel conspiracy thinking here. Don’t try to spread FUD, especially against reliable privacy-enhancing software. Extraordinary claims require extraordinary evidence. Show credible sources. -
Don't accuse others of shilling
Send honest concerns to the moderators and/or admins, and we will investigate. -
Do not remove your help posts after they receive replies
Half the point of asking questions in a public sub is so that everyone can benefit from the answers—which is impossible if you go deleting everything behind yourself once you've gotten yours.
view the rest of the comments
not sure , but maybe it is media codec/encoding related?
You could maybe try https://addons.mozilla.org/en-US/firefox/addon/enhanced-h264ify/ to check.
It's not, because my CPU supports VP9 hardware decoding.
By anychance, do you have free ram? Sometimes this happen when the ram is not available... so yeah.. You should check it first. Also check about:memory I guess
Yes
Is the
about:cacheis full? Or it's too small? I mean if it's to small it could be the cause.I didn't know about that. It does seem small. It's just 32 MB. So I googled around and
changed
browser.cache.memory.capacityvalue from-1to1000000and changedmedia.cache_readahead_limit/media.cache_resume_thresholdto999999but I didn't notice any difference. Rebuffering still happens.What I did notice was that after hitting the replay button, if I press right arrow quickly enough to skip forward (40% or more), the buffer reppears and my network activity reflects that.
So it seems to me is that Firefox caches about 60% of the video (latter half) and when you replay it, it starts rebuffering the lost 40% of the first half of the video. I reverted my settings back to default values (the 3 prefs I mentioned above) and it still behaves this way.
ugh, I'm out of idea tbh. Seems you need to ask others about it. Also are your video in 2k or probably 4k? or it's normal 1080 or even only 720?
Same. I even came across this comment after doing that. Did everything it said (
browser.cache.offline.enableperf wasn't there for some reason, so I made one) and still no change. Changed the values of perfs mentioned in my post again as well, combined with that comment's proposed changes but still nothing.And yeah, it's 1440p but I've tested this on 1080p videos as well. Length of 1440p video is 2-3 mins and the 1080p one is just over 11 mins.
Honestly, I give up at this point. Btw, thank you so much for trying to help.