attachment 739929 [details] reports that when we switch to a new application, we see MEM_PRESSURE GCs which might take a lot of time, including one which is taking up to 2.6 seconds to complete. Based on marionette log, this GC pause of 2.6 seconds should be at the end of the browser load, likely done in another process. The log does not explicit which application is having this MEM_PRESSURE GC, but I guess this is likely the home screen. We should probably delay the MEM_PRESSURE GC when we are running multiple applications, such as it does not impact the start-up time of the next application.
Whenever an app goes into the background, we send a memory pressure event to this app in order to minimize after a few sec.
> We should probably delay the MEM_PRESSURE GC when we are running multiple applications, > such as it does not impact the start-up time of the next application. It would be helpful if you could try to determine whether the GC we're running in this unknown process is impacting startup time. Otherwise, everything is behaving as expected. I don't expect a startup time impact from this, but it's possible given how broken setpriority is.
Mass-closing JS bugs for which the platform is Gonk (Firefox OS), since Firefox OS is gone. Feel free to re-open if still valid.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.