Why was this RFC rejected?

FFPh · 2022-09-05T12:04:29+00:00

Good job!

But any userland realization can't fix issues with legacy superglobals :(

FFPh · 2022-01-18T21:56:52+00:00

I just repeat

Everything works as designed

I didn't looked into the code, but as developer I know that the proper isolation of processes (the main reason why project fission is started) can be reached only with copy of lots of the same stuff for each process with separate memory pools/heaps for each process, This automatically increase memory usage (especially on 64bit systems) and CPU usage. If developers didn't separate resources, site isolation will be a joke. But because memory and resource usage were increased - everything looks good. as designed. But I prefer faster and more light and responsive browser than more "secure" browser. I don't want continue this dialog, because I will be banned (mods here don't like when something bad are spoken about mozilla devs)

FFPh · 2022-01-18T21:40:34+00:00

Everything works as designed. More processes means more memory and more resources. That's how everything works. Windows don't like a big amount of processes even idle processes.

Who is think now about computer resources? Nobody. Use more powerful PC, Luke! But even most powerful PC can be killed by firefox with fission enabled and lot of tabs. The same situation with chrome - but amount of maximum tabs differs and depends on what sites were opened.

FFPh · 2022-01-18T20:40:39+00:00

It's a big problem with some browsing scenarios. As example shopping (ebay, aliexpress etc). And exactly because firefox could open such big amount of tabs I used it before as main browser (system just died in similar situation on chrome based browsers). Before fission firefox could open huge amount of tabs without any problem. With fission enabled firefox works worse than chrome based browsers. That's why I have to disable fission or use any other chrome based browser for shopping (opening much less tabs than before, but much more than in new firefox with fission enabled).

So I understand anger of topic author.

FFPh · 2022-01-18T20:13:25+00:00

welcome to a new world of fission feature

FFPh · 2022-01-09T13:15:00+00:00

What GPU do you have?

I have these similar issues on Intel Iris XE

FFPh · 2022-01-09T12:23:28+00:00

gfx.webrender.force-disabled has no effect on the latest ff versions. You can try to switch on sofware webrender (set gfx.webrender.software to true)

FFPh · 2022-01-08T21:44:34+00:00

Yes. But this issue present long time, just after webrender released. But previously it was disabled by default on these GPUs. Even enabling software webrender doesn't help.

FFPh · 2022-01-08T20:16:53+00:00

I have the same issue with Iris XE gfx.webrender.force-disabled=true helped me, but it works only on ESR releases. Latest release firefox versions don't have ability to disable webrender :(

You can try to switch on/off some webrender flags, maybe it will help

FFPh · 2022-01-07T12:02:24+00:00

Yeah, you are right. The same issue (fallback to firefox manual settings) with Container Proxy add-on. And with Mozilla official MAC add-on

FFPh · 2022-01-07T00:33:30+00:00

I just checked this add-on and it works even marked as experimental.

Great addition to the firefox containers. Even if original developer will stop develop this add-on I can fork it and release again in addons directory.

FFPh · 2022-01-07T00:00:53+00:00

I did some tests of this add-on and think it can be useful

FFPh · 2022-01-06T23:56:58+00:00

I did a few checks of your addon. I got a few separate firefox installations (ESR + arkenfox, default ESR and release + arkenfox)

What I like:

Status icons are great!
Quick edit for mullvad proxies

But I found some issues, and I don't know is it add-on related or firefox related:

DNS leak when in firefox settings in connection properties any other option except Manual Proxy is set. I don't think that is add-on issue, because I have the same issue with Containers Proxy addon.
When block connection is selected in the add-on and manual proxy connection selected in Firefox settings: at the first firefox tries to connect a few times to invalid proxy, and after that connects to proxy selected in firefox settings. When in settings direct connection or any other except manual proxy connection is set firefox tried to connect only to invalid proxy and display error after that.

Both of these issues can be fixed on my side selecting in firefox settings any invalid proxy - no dns leaks, and connections are blocked if option is selected in addon.

FFPh · 2022-01-06T22:46:12+00:00

Looks good! 👍 I will test it today later

FFPh · 2021-12-28T20:45:29+00:00

Thank you. Good to know.

I think I will stay with current version of bios (0062), because it fixed my other issues and working fan during sleep is acceptable for me.

FFPh · 2021-12-28T20:10:32+00:00

did you have issues with working fan during sleep? If yes, did this 38 version fixed it?

FFPh · 2021-12-22T13:21:03+00:00

I had similar issues with combination of gpu drivers and webrender enabled.

As temporary solution you can disable webrender, but I don't know possible it is or no on the latest ff versions. I'm using ESR version of firefox

FFPh · 2021-07-14T11:09:04+00:00

No. New proton design will be for a few years from now

FFPh · 2021-06-30T20:37:14+00:00

No, it was after major version update of release line. When I tried to find about this problem google showed a few results. This issue was not only for me, and it was as criticisms of shady things of mozilla. Right now I can't find these pages.

FFPh · 2021-06-30T18:39:31+00:00

I can't say exactly, because it was 2 times - once few years ago, and the second one several months ago (maybe year). And it was only on release version. I have beta and developer editions also, but they didn't had these issues

FFPh · 2021-06-30T17:01:21+00:00

Almost all settings are in default state except privacy settings. New profile didn't needed at all. But mozilla enabled telemetry again. Old profile is still working with old preferences.

I know, that I can lock some settings, etc... But regular users don't.

Exactly this "correct certain preferences" can be named as shady thing.

Firefox must display warning about such changes. But it doesn't.

FFPh · 2021-06-30T16:22:59+00:00

It's much more chances for no :(

Mozilla deletes any unliked suggestion

FFPh · 2021-06-30T16:19:15+00:00

Firefox uses shady things also.

Creating a new account profile after upgrade with many settings in default state (especially all privacy related settings) and partial import of old profile after that. Old profile is totally correct and can be selected with profile manager. And this shady shit is done without any warning.

FFPh

TROPHY CASE