Closed Bug 1499330 Opened 7 years ago Closed 7 years ago

Youtube Videos Laggy since FF60

Categories

(Core :: Audio/Video: Playback, defect, P3)

62 Branch
x86
Linux
defect

Tracking

()

RESOLVED INACTIVE

People

(Reporter: jan-peter, Unassigned)

References

Details

(Keywords: regressionwindow-wanted)

User Agent: Mozilla/5.0 (X11; Linux i686; rv:62.0) Gecko/20100101 Firefox/62.0 Steps to reproduce: Try to play some Youtube Videos. Actual results: It Plays laggy. Expected results: It should play normaly as in smplayer
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Hello Jan-peter, I can't reproduce your issue. A. Does it also occur in the case of another browser, like Chrome? B. If yes, Please test if the issue is reproducible in safe mode, here is a link that can help you: https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode C. If it still reproduces in safe-mode, then we have to move on and test whether it reproduces in the latest Nightly and record a performance profile: Please download Firefox Nightly from here: https://nightly.mozilla.org/ ,retest the problem AND record a performance profile. These steps will help you through the process: 1. Install this (https://perf-html.io/) add-on on the Nightly browser. 2. Click on the add-on button from the top right of the page (Geeko Profiler) and click the "Start" button. 3. Reproduce the issue; (Some visible memory/network usage issues should be of great help). 4. Click on the add-on button from the top right of the page (Geeko Profiler) and click the "Capture profile" button. 5. A new page will be displayed (with the actual performance profile), but now you have to share it: Tap on the "Share..." button from the top-right corner of the page, then again "Share' on the pop-up displayed and copy the link back here. Thank you for your contribution!
Component: Untriaged → Audio/Video: Playback
Flags: needinfo?(jan-peter)
OS: Unspecified → Linux
Product: Firefox → Core
Hardware: Unspecified → x86
Hello In other Browsers such as Opera, Vivaldi or Chromium it works fine. Withother Players such as smplayer, VLC, XINE Player and so on it wsorks fine to. Only in Firefox and Thunderbird since Version 6*.*.*.* upwards it stutters. I´ve tried th Safe Mode for both Programms with no change in behaviour. The only thing I can see in htop is that in normal use there are much fewer threads than at Playing youtube Videos (Normal between 4 and 32, at playing youtube between 64 and XXX) I am using Firefox and Thunderbird on 5 PC´s and on all of them the same behaviour occurs. I will try that out and will then post here.
Flags: needinfo?(jan-peter)
By the Way the same goes for Audio Playback MP3, M4A and so on.
669 ms event processing delay in content process, but only 237ms of that is recorded by the profiler. Perhaps the rest is not accounted because the CPU is busy with other threads. I don't see any decode threads in the profile, and so I guess the CPU might be busy on decode threads that are not profiled. Of the accounted time during this delay: 78+62 ms running youtube script 44 ms painting If the change from 59 to 60 is very noticeable and reproducible, then the best way to identify the cause of the problem is probably to find the changeset involved using https://mozilla.github.io/mozregression/.
Priority: -- → P3
Hi Jan-peter, Since I can't reproduce your issue, I have to ask you to help again. As Karl Tomlinson mentioned above, a regression of this issue should probably be performed. This means that you should use a tool called mozzregression to investigate which build introduced this issue. If you're willing, the information on the tool is available at http://mozilla.github.io/mozregression/. Thank you for your contribution!
Flags: needinfo?(jan-peter)
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → INACTIVE

Solution found KDE Databases and Backgrounds had used to many Cpu Power.

Flags: needinfo?(jan-peter)
You need to log in before you can comment on or make changes to this bug.