M O V A Я d Z I L L A

>>60898193
I always knew Firefox is shit.

and OP is a fag

>multiprocess is disabled because an addon would either stop working, not work properly or cause performance issues
wtf i hate mozilla now!!!

it's been like this for two years. blame your addons dev for not fixing it.

>>60898331
I forced-enabled multiprocess support and everything's working perfectly. Mozilla just never got around to whitelisting addons, so for most users it's disabled by default. They're just going to let old addons get deprecated and only support the new style addons.

Instead of, you know, supporting their user-base.

>>60898193
>mfw I'm still on 53 because of slow mint repos

>>60898193
https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter/
Here you go

>>60898370
The old addon design is shit, they finally realised it, so it's a good thing. Insecure things should deprecate.

How do I enable multi process?

>>60898430
about:config
New Boolean
browser.tabs.remote.force-enable
true

>>60898418
This. WebExtension, while a bit more limiting (we'll know just how much by November when Firefox 57 hits release channel), is better than the current one. If your addon becomes deprecated by this time it's because the developer is too lazy to convert it to a WebExtension and none of the users are competent enough to fork or maintain it.

>>60898469
Done. So basically this makes Firefox work like chrome? Each tab is a separate process right? So for example if /g/ crashes because it is fucked up it won't affect my other open tabs.

>>60898493
>because the developer is too lazy to convert it to a WebExtension
Oh yeah. What about extensions like Classic Theme Restorer which is technically impossible to pull off due to like 50 APIs missing?
Developers are getting fucked by Mozilla and there is nothing they can do about it.

File: 1480975539128.jpg (156KB, 1080x1080px) Image search: [Google]

156KB, 1080x1080px

>>60898469
Dis nigga knows what's up.

>>60898537
> Each tab is a separate process right?
No, it's only 4 processes right now, but you can set way more in about:config. Chrome isn't process per tab either, but per domain.

>>60898537
It's not one process per tab because currently it would use too much RAM but at least it separates the main process from the content so that if the content crashes it won't crash the browser and it also makes the UI feel more responsive since one page (there are extreme cases but we're talking regular use) can't make the UI unresponsive. dom.ipc.processCount controls how many content processes will be used, the tabs will be distributed among this number. If you fell for the 16 GB RAM meme you can set it to 50 or something (4-5 per 1 GB of RAM).