Playing video on Videobin.co results in high CPU - in ntoskrnl.exe, Windows 7
Categories
(Core :: Graphics, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox73 | --- | affected |
People
(Reporter: therubex, Unassigned)
Details
(Keywords: perf)
Attachments
(2 files)
dxgmms1.sys 6.1.7601.24513
(Potentially NSFW website including popups & other "stuff" so proceed, cautiously.)
URL: https://videobin.co/pfltkg6ue425
Click to play the video.
(Might take a second or third or forth click... due to aforementioned, "stuff".)
Note the "stars" falling... (which I don't believe is the issue).
Eventually the video should start to play - perhaps (but in any case, so long as it attempts to start to load, you should see the issue).
Results:
On Win7 x64, in Mozilla browsers, the (Windows) process "NT Kernel & System" (aka "System" aka ntoskrnl.exe) starts to eat 50% CPU (on a 4 core processor), greatly affecting overall computer system performance.
Other browser:
On Google Chrome, resultant CPU usage remains in chrome.exe, leaving ntoskrnl.exe unaffected.
Other:
Perhaps it is not even the actual video playback that is the issue, but the web page itself? Not sure? In any case, visiting the site greatly affects one's computer system - and it does this outside of "firefox.exe" itself (which may only actually use < 10% CPU during this time).
It's possible that this is being caused by differences in performance between the video decoders used between Firefox and Chrome. In the case of Firefox we use a windows decoder, which could explain the CPU usage you're seeing, while Chrome uses a different decoder.
Could you capture a profile run using the Firefox Profiler? If you could set the threads being captured to '*' by putting that value in the 'Add custom threads by name:' text box that will capture all threads. Then could you link the profile on this bug? That will help give us a better idea on if anything else on the page is eating resources.
Note the "stars" falling... (which I don't believe is the issue).
Perhaps it is not even the actual video playback that is the issue, but the web page itself? Not sure?
Well, at this point, I'm no longer able to duplicate the issue.
Currently, FF (74) is using ~15% CPU, all contained within "firefox.exe", ntoskrnl.exe unaffected.
Perhaps it was the "stars" falling?
(Somewhere, more recently, I've seen stars...)
Or perhaps it was an issue on their site, that they've since rectified?
In any case, I find it rather disturbing, that the issue occurred, that the issue manifested itself "outside" of FF, & that it was so intrusive to the computer at large.
Aha, got it!
From Google Cache, with stars & high CPU.
Simply did a search, site:videobin.co, & luckily, quickly found a cached link that displayed the issue.
No telling how long it will last...
(In reply to therube from comment #5)
Is this what you need?
snip
There should be a share button that should upload the profile and give a smaller link. Would that happen to be a profile link from the page on the google cache with the worse performance?
Yes.
New Profile.
Open (orig) videobin.co link.
Issue not present.
Find "bad" (Google cached) videobin.co link.
Issue present.
The profile you linked does show a lot of time being used to do painting. Based on the information you've provided it seems possible that the snow being painted by the page is done in a way that is degrading performance.
With regards to seeing the high CPU usage in non-Firefox process, this can be a product of that Firefox needs to interact with the operating system to perform certain operations (like decoding a video, or asking it to render something). If the operating systems itself is performing calculations that use a lot of CPU, this can result in behaviour like you see here.
I suspect this is actually an issue more closely related to graphics. However, since the page has removed the snow/stars, and since we don't know how long the cache will stay up, I'm going to resolve this. If they return the effect to the page, please reopen this and we can see if graphics are able to diagnose what's going on.
|
Reporter | |
Comment 10•4 years ago
|
||
The point is not that the site is not causing particular issues - now.
The point is not that the cached page may go away at some point.
The point is that there is an issue - with FF, that at the least may hang FF - totally, that negatively impacts one's entire computer system - greatly.
If not "this" website, there will be another, that ends up likewise affecting FF, to the detriment of it's users.
The OS performing calculations is not the issue.
There is a direct relationship between that page (now the cached page with the stars - which is still live) & FF.
Close FF, & the issue subsides. Open FF to an affected page, & the issue returns.
Other (non-Mozilla) browsers were not affected.
Other Mozilla browsers, other then "FF Nightly" (including "legacy" browsers) are affected.
Have you even visited the cached page, yourself, to see what it may or may not do on your end?
Instead of AV/Playback (which may not even be the issue), I'm thinking I probably should have just posted this is "FF General" & let them ferret it out to where they believe it should have gone.
|
||
Comment 11•4 years ago
|
||
The priority flag is not set for this bug.
:bryce, could you have a look please?
For more information, please visit auto_nag documentation.
(In reply to therube from comment #10)
snip
My explanation as to why you are seeing the CPU usage where it is was in response to comment 3 given that you seemed concerned as to why it was happening there.
I have visited the cached page and did not reproduce the issue on my machine. However, as I indicated above, I believe the issue is graphics related. To expand on that, based on the profile, I think it's a combination of the page's code drawing a lot of separate elements and how Firefox is drawing. I'm going to move this to the graphics component.
|
||
Updated•4 years ago
|
|
||
Updated•2 years ago
|
Description
•