Viewing profile — gcp

I don't think Firefox has the access permissions needed to read MCE status, and the vast majority of our users don't have ECC, let alone they're going to run memtest86(+) after a F…

No.

Deduplicating and identifying the source of a crash point is surprisingly hard, to the point that “it’s the only crash of its kind” could be a bug in your logic for linking issues.…

Did you actually read the posts that started this topic, or are you being an ass for no reason? Hint: No-one is claiming memory is to blame for 100% of the Firefox crashes. No-one …

I'm quite confident to say that millions of people use Firefox to comment on Reddit or similar sites every day, or write long posts, without seeing this problem. Without knowing mo…

You were seeing issues from the graphics driver, not Firefox. Any memory allocation failing within the browser forces an instant crash unless the callsite explicitly opts in to han…

Yeah, Dark Reader is known to totally plummet Firefox performance. Not sure if it's a coding issue in the Firefox version of Dark Reader, or it's hitting some slow path in Firefox …

It helps if you file bugs in Bugzilla. You can link to them here, there's a good chance a developer will find them.

Change tends to mean things like exciting new spying and UI regressions Or missing out on new anti-fingerprinting and anti-tracking improvements. Note that adblockers don't general…

The whole point of the about:restartrequired warning is to avoid this problem. If you're crashing, I hope you've been filing bugs.

This is how Mozilla's own updater works (if you use the .tar.gz version), but the distro package updater just overwrites everything without waiting and applications like Firefox ha…

What determines "excessive"? In this case it's for a security feature that Chrome lacks(!).

Did you report this on Bugzilla? Even if it's not Firefox's fault if you don't report it no-one knows about the issue. Recent versions of Firefox allow you to block some stuff like…

One reason why it shipped on Windows first is that the situation is more serious there. The article goes into details why the different overcommit behavior is more problematic on W…

Because for some people their open sites, and the ability to switch quickly between them, is the most important use of their machine and what they want their RAM to be used for.

It wasn't enabled by default because it didn't work well enough. Getting better low memory triggers was a key to making this an overall benefit, and not just a user annoyance.

>very rarely Firefox would crash The feature stops (or reduces the likelyhood) of that happening. It literally is made to trigger in a situation where the alternative is to crash. …

>though it's not clear to me what the difference is This one works well enough that we can default it on :-) The previous one didn't reliably detect low memory situations and you c…

That's definitely something we would want to do, but it requires a (very) reliable measurement method for this kind of memory pressure. If it's not reliable, the browser unloads ta…

>No thanks, I'd rather get more RAM or swap space for paging. As the article explains, if you have enough swap you'll never trigger this. It activates right before you'd have crash…

People on low memory machines, or people on big boxes that read some article about how swap makes your SSD die and tried to disable Windows swapping (or downloaded some "optimizati…

The original ticket seems to indicate this is a leak in a Windows accessibility service and so far there was no luck in finding a way to avoid it. That sucks.

Paste a few links from about:crashes here. If you click on them, you might find the associated bug (if it exists). Firefox should literally never crash. If it does, that's a seriou…

Paste a few links from about:crashes here. If you click on them, you might find the associated bug (if it exists). Firefox should literally never crash. If it does, that's a seriou…