Thanks! There are so bugs filed about similar issues, I wasn't aware of that one. I think there might be two (or more) different bugs. There's one case where the process is unresponsive because it is using 100% CPU, chugging through work that built up during the sleep. Firefox eventually recovers. And then there's another case where there's ~0% CPU and we just don't paint. I think bug 1415923 was initially about the 0% CPU case, but has now morphed into the 100% CPU case. Let's use this bug for the 0% CPU case.
Bug 1682713 Comment 36 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks! There are so many bugs filed about similar issues, I wasn't aware of that one. I think there might be two (or more) different bugs. There's one case where the process is unresponsive because it is using 100% CPU, chugging through work that built up during the sleep. Firefox eventually recovers. And then there's another case where there's ~0% CPU and we just don't paint. I think bug 1415923 was initially about the 0% CPU case, but has now morphed into the 100% CPU case. Let's use this bug for the 0% CPU case.
Thanks! There are so many bug reports filed about similar issues, I wasn't aware of that one. I think there might be two (or more) different bugs. There's one case where the process is unresponsive because it is using 100% CPU, chugging through work that built up during the sleep. Firefox eventually recovers. And then there's another case where there's ~0% CPU and we just don't paint. I think bug 1415923 was initially about the 0% CPU case, but has now morphed into the 100% CPU case. Let's use this bug for the 0% CPU case.