http://bugzilla.opensuse.org/show_bug.cgi?id=1076811 http://bugzilla.opensuse.org/show_bug.cgi?id=1076811#c1 Wolfgang Rosenauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wolfgang@rosenauer.org --- Comment #1 from Wolfgang Rosenauer --- I do not have an idea why the rescue system behaves that way. Is there a way to get or create a VM with such a system. (Sorry, I'm a bit async wrt rescue systems.) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1076811 http://bugzilla.opensuse.org/show_bug.cgi?id=1076811#c3 --- Comment #3 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. -- You are receiving this mail because: You are on the CC list for the bug.