Comment # 3 on bug 1076811 from Wolfgang Rosenauer

hmm, for me the question is: Do we really need to do anything from an
application point of view. Some applications are getting more demanding over
time and Firefox is unfortunately but somehow understandable affected.
Now there is a good chance that we find a workaround as for example disabling
e10s or limit e10s to just one content process. This would be possible via
local configuration but that is not something I would like to ship as a
default.
So if we introduce a hack (like changing values in the openQA run we also need
to accept that openQA is testing something which is not the same what is
hitting a user in real life.
So from an application perspective I do not see real alternatives.