3. Implement Electrolysis (https://wiki.mozilla.org/Electrolysis). From my observation, the real problem with Firefox is not the memory usage but its slowness.
Electrolysis does nothing to solve this, which is why it was abandoned.
I'm thinking that if Firefox has Chrome-like multi-process architecture, the interface would be more responsive and memory management would be even better.
Memory usage is far worse with multi-process, it's one reason Firefox uses less memory than Chrome.
At least, it could make the UI more responsive. Even though multi-process may use more memory, I think it's easier to reclaim/cleanup unused memory when for example, closing a tab.
Electrolysis does nothing to solve this, which is why it was abandoned.
I'm thinking that if Firefox has Chrome-like multi-process architecture, the interface would be more responsive and memory management would be even better.
Memory usage is far worse with multi-process, it's one reason Firefox uses less memory than Chrome.