Batu69 Posted September 5, 2016 Share Posted September 5, 2016 With multi-process Firefox slowly rolling out to stable channel installations of the browser, further work is done on improving the feature for all Firefox users. Mozilla made the decision to roll out the new multi-process architecture with a single content process initially that is separated from the browser core. The company plans to change that by adding more processes to Firefox.The feature needs to be stabilized first however as it is plagued by a couple of bugs currently. Another improvement that is still in the works is sandboxing which will improve security once it lands. One core difference between Firefox's multi-process architecture and that of Google Chrome is that Firefox will never use Chrome's one process for every site system. The main reason for that decision is RAM usage, as it can quickly go out of hand. Mozilla's initial implementation uses about 20% more memory when compared to vanilla Firefox without multi-process enabled. Memory usage of Subprocesses Mozilla landed a new feature in Firefox 51 Nightly recently that lists the memory usage of each process in the browser itself. All you need to do is load about:performance in Firefox to get a listing of each process, and the memory it uses. If you have not changed the number of processes, you get one parent process and another that is used for the content listed on the page. Each content process is listed with its process ID which makes identification easier. While there is no option to deal with a process right from the about:performance page, you may open the Task Manager to locate and kill a misbehaving process using its ID; this should not have any effect on the parent process or other processes used by Firefox. The new feature is comparable to Chrome's Task Manager which lists memory use and process IDs as well. Chrome however has options to end a process right from within the Task Manager, and it lists network and cpu use of each process on top of that. One issues with Firefox's memory usage listing on the page is that there is no indication about the sites that are open in any given content process. It would be useful to have a listing of each site open in a content process, as it may help analyze why RAM usage shot through the roof. It will take a while before the new feature lands in Firefox Stable. (via Sören) Article source Link to comment Share on other sites More sharing options...
RejZoR Posted September 5, 2016 Share Posted September 5, 2016 20% more? With almost 500MB on a tablet with just 2GB, that's 600MB. Ridiculous. Link to comment Share on other sites More sharing options...
truemate Posted September 5, 2016 Share Posted September 5, 2016 yea.. thats why mozilla SUCKS regarding memory.. this the only browser which i have seen that eats to much of memory. Link to comment Share on other sites More sharing options...
Administrator DKT27 Posted September 5, 2016 Administrator Share Posted September 5, 2016 5 hours ago, RejZoR said: 20% more? With almost 500MB on a tablet with just 2GB, that's 600MB. Ridiculous. Going by this article posted previously,they might not do it on mobile: Quote While most may not remember, Electrolisis is not Mozilla’s first attempt to bring a multi-process architecture to Firefox. Six years ago, Project Candle brought a multi-process architecture to Firefox on mobile. The company abandoned the efforts after noticing it was creating a bottleneck on mobile, according to Dotzler. Today the Firefox mobile browser runs as a single process but with advancements in the processing power of smartphones, it is possible that additional content processes could come to mobile again in the future. But I agree, Firefox on mobile is a big problem. Back to the main topic. I personally think Firefox should make use of the CPU cores if they do this. By that I mean, one process using on CPU core, another one using another. This way, no one process can slow the PC. Link to comment Share on other sites More sharing options...
pc71520 Posted September 6, 2016 Share Posted September 6, 2016 On 5/9/2016 at 6:21 PM, truemate said: that's why mozilla SUCKS regarding memory It will get worse when electrolysis will be officially released. Link to comment Share on other sites More sharing options...
truemate Posted September 7, 2016 Share Posted September 7, 2016 17 hours ago, pc71520 said: It will get worse when electrolysis will be officially released. thats why i rarely use mozilla... try to use it on some streaming sites where flashplayer in main video player or any site where tons of pics are posted.. firefox starts shivering lol eats so much of memory portable chrome dev & opera dev/beta r just fuking awesome.. so fast even IE11 is faster then mozilla Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.