KoolKai

joined 1 year ago
sorted by: new top controversial old
Why does Firefox on Windows take so much RAM? in c/[email protected]
[–] [email protected] 1 points 1 year ago

If Firefox is using an unexpected amount of RAM, report a bug by following the steps below:

  1. Open about:memory in a new tab.
  2. Click Measure and save...
  3. Attach the memory report to a new bug
  4. Paste your about:support info (Click Copy text to clipboard) to your bug.

If you are experiencing a bug, the best way to ensure that something can be done about your bug is to report it in Bugzilla. This might seem a little bit intimidating for somebody who is new to bug reporting, but Mozillians are really nice!

If you prefer not to open a bug, you can instead reduce the number of content processes used by Firefox to a lower amount by going to about:config and changing dom.ipc.processCount.webIsolated to a lower number.

1
Firefox support for Windows 7, 8 and 8.1 (blog.mozilla.org)
 

With Firefox 115, users on Windows 7, Windows 8 and Windows 8.1 will automatically be moved to the Firefox Extended Support Release (ESR).

Can't use hardware acceleration on archlinux, how do I make it work? in c/[email protected]
[–] [email protected] 1 points 1 year ago

Please help, I cant watch videos!

You could always disable hardware video decode acceleration and continue to watch videos.

Firefox has surpassed Chrome on Speedometer in c/[email protected]
11
Firefox has surpassed Chrome on Speedometer (treeherder.mozilla.org)
Replaying a video on YouTube makes it buffer all over again instead of it playing instantly like Chrome does. Is there any fix for this? in c/[email protected]
[–] [email protected] 1 points 1 year ago (1 children)

I just compared the behavior in both Chromium and Firefox on my machine, and as far as I can tell, they act the same.

Steps to reproduce:

  1. Open a video: https://www.youtube.com/watch?v=erQ_9yEz0ls
  2. Play the last 10 seconds
  3. Click "replay" button in the YouTube player

What happens:

The buffer is cleared in both browsers.

What are you seeing that is different?

23
Take Back the Web (pauloroger.dev)
 

Maybe you are already a Firefox user, we are part of a minority on the web today, and think that this text is not for you. You’re probably right, but I’d like to make a few points here and ask for your help in taking the web back before it’s too late. And if you don’t use Firefox, you’ve been using some version of Chromium (Chrome, Edge, Opera, Brave or Vivaldi) a few years ago this wouldn’t necessarily be a bad thing, but today it’s bad for the health and freedom of an web that respect privacy and is not controlled by capitalist corporations, the so-called Big Techs.

Firefox 115 released in c/[email protected]
[–] [email protected] 1 points 1 year ago

If you want to find the bug, you can run a mozregression to find what broke it (using 114 as your last known good release and 115 as your bad release).

Please reach out if you need help with this.

You can use your profile to test this pretty easily.

May and June were good months for Firefox's Speedometer performance compared to Chrome. in c/[email protected]
45
May and June were good months for Firefox's Speedometer performance compared to Chrome. (mozilla.social)
 

May and June were good months for Firefox's Speedometer performance compared to Chrome. We're closing in while Chrome seems fairly static. In this visualization, lower in the graph is better. From https://arewefastyet.com/win10/benchmarks/overview?numDays=60.

5
21 years ago this summer Firefox got real. (twitter.com)
 

21 years ago this summer Firefox got real. For some months it was mostly just tinkering, but with Blake's internship and collabs with Hyatt, PCH contributing, Hewitt getting more involved, Kerz, myself and a couple others working on theme stuff, things were getting serious.

5
Introducing the MDN Playground: Bring your code to life! (developer.mozilla.org)
 

MDN is launching a code Playground. Users can prototype ideas and expand all live samples into an interactive experience.

32
On Monday morning we (Mozilla) detected a very large crash spike affecting Firefox users on Linux, specifically on an older version of a Debian-based distribution (fedia.io)
 

On Monday morning we (Mozilla) detected a very large crash spike affecting #Firefox users on Linux, specifically on an older version of a Debian-based distribution. It turned out to be an interesting bug involving the #Linux kernel and #Google JavaScript code so let me tell you about it. A thread 🧵

241
On Monday morning we (Mozilla) detected a very large crash spike affecting Firefox users on Linux, specifically on an older version of a Debian-based distribution (fedia.io)
 

On Monday morning we (Mozilla) detected a very large crash spike affecting #Firefox users on Linux, specifically on an older version of a Debian-based distribution. It turned out to be an interesting bug involving the #Linux kernel and #Google JavaScript code so let me tell you about it. A thread 🧵

6
On Monday morning we (Mozilla) detected a very large crash spike affecting Firefox users on Linux, specifically on an older version of a Debian-based distribution (fosstodon.org)
 

On Monday morning we (Mozilla) detected a very large crash spike affecting #Firefox users on Linux, specifically on an older version of a Debian-based distribution. It turned out to be an interesting bug involving the #Linux kernel and #Google JavaScript code so let me tell you about it. A thread 🧵