The problems many have noticed with TBB performance with current VM configurations are all traceable to Firefox’s transition to a multiprocess model. One solution is to simply push up VM resource allocation. Meanwhile a more pragmatic solution is to change the behavior of the software to become more efficient. We lose out on upstream sandboxing work whenever it materializes, but we have firejail to make up for it.
Does turning off E10 make TBB fingerprintable? (Tor dev question)
Is this workaround future proof? (Firefox question)
Can we use a similar workaround like I2P browser to set these booleans in about:config for the default TBB install?
How it is done: