Closed
Bug 1473290
Opened 7 years ago
Closed 4 years ago
(Page is stuttery to scroll. Uses lots of CPU (brainyquote.com/authors/karl_pilkington)
Categories
(Core :: Graphics: WebRender, defect, P2)
Core
Graphics: WebRender
Tracking
()
RESOLVED
FIXED
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [gfx-noted])
Attachments
(1 file)
27.41 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0
Build ID: 20180703220118
Steps to reproduce:
go to https://www.brainyquote.com/authors/karl_pilkington
Scroll with the touchpad
Actual results:
page is micro-stuttery to scroll. When i checked the CPU use, it was using 50%-90% of a Quad core processor
Expected results:
not so
https://perfht.ml/2lUm00s
Updated•6 years ago
|
Updated•6 years ago
|
Blocks: wr-perf
Summary: Page is stuttery to scroll. Uses lots of CPU → (Page is stuttery to scroll. Uses lots of CPU (brainyquote.com/authors/karl_pilkington)
Updated•6 years ago
|
Priority: P2 → P3
Updated•6 years ago
|
Priority: P3 → P2
Reporter | ||
Updated•6 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 1•6 years ago
|
||
Can you still reproduce this? Scrolling is super smooth for me, and CPU time is ~2ms/frame.
Reporter | ||
Updated•6 years ago
|
Flags: needinfo?(mayankleoboy1)
Reporter | ||
Comment 2•6 years ago
|
||
still feels micro-stuttery.
Here is a profile: http://bit.ly/2JrtfrI
Flags: needinfo?(mayankleoboy1) → needinfo?(matt.woodrow)
Comment 3•6 years ago
|
||
Can you please post your about:support contents.
27% of rendering time is spent within calls to VerifyVersionInfoW, coming from your intel gpu driver, that strikes me as very unexpected.
Flags: needinfo?(matt.woodrow) → needinfo?(mayankleoboy1)
Reporter | ||
Comment 4•6 years ago
|
||
about:support
Flags: needinfo?(mayankleoboy1) → needinfo?(matt.woodrow)
Reporter | ||
Comment 5•6 years ago
|
||
(In reply to Matt Woodrow (:mattwoodrow) from comment #3)
> Can you please post your about:support contents.
>
> 27% of rendering time is spent within calls to VerifyVersionInfoW, coming
> from your intel gpu driver, that strikes me as very unexpected.
FWIW, I see large time spent in VerifyVersionInfoW in almost all WR profiles I have taken.
Comment 6•6 years ago
|
||
(In reply to Mayank Bansal from comment #5)
> (In reply to Matt Woodrow (:mattwoodrow) from comment #3)
> > Can you please post your about:support contents.
> >
> > 27% of rendering time is spent within calls to VerifyVersionInfoW, coming
> > from your intel gpu driver, that strikes me as very unexpected.
>
>
> FWIW, I see large time spent in VerifyVersionInfoW in almost all WR profiles
> I have taken.
That seems really problematic. I can't reproduce anything similar on my Intel card, including with Kaspersky installed.
It seems unlikely that just your specific driver/device version would be calling VerifyVersionInfoW, so I'm assuming that the kernel32.dll/ntdll.dll version of it is just really slow for some reason.
Is there anything else interesting about your Windows install that might result in this being really slow?
Flags: needinfo?(matt.woodrow)
Reporter | ||
Comment 7•6 years ago
|
||
(In reply to Matt Woodrow (:mattwoodrow) from comment #6)
> (In reply to Mayank Bansal from comment #5)
> > (In reply to Matt Woodrow (:mattwoodrow) from comment #3)
> > > Can you please post your about:support contents.
> > >
> > > 27% of rendering time is spent within calls to VerifyVersionInfoW, coming
> > > from your intel gpu driver, that strikes me as very unexpected.
> >
> >
> > FWIW, I see large time spent in VerifyVersionInfoW in almost all WR profiles
> > I have taken.
>
> That seems really problematic. I can't reproduce anything similar on my
> Intel card, including with Kaspersky installed.
>
> It seems unlikely that just your specific driver/device version would be
> calling VerifyVersionInfoW, so I'm assuming that the kernel32.dll/ntdll.dll
> version of it is just really slow for some reason.
>
> Is there anything else interesting about your Windows install that might
> result in this being really slow?
I used to think these times were normal, until you said its not!
I have Win10 october update, but the large times spent under VerifyVersionInfoW has been there much before that.
I have maybe changed some settings in the Intel control panel, but I try to set all settings to "Let the application decide".
I dont really know what else to add... i would be happy to run diagnostic builds and provide you with logs or something
Reporter | ||
Comment 8•6 years ago
|
||
just to make sure that there was nothing funky going on, I restarted my machine, and then took a profile:
http://bit.ly/2RmkYYW
Reporter | ||
Comment 9•6 years ago
|
||
Another page where large time is spent in VerifyVersionInfoW is http://themaninblue.com/experiment/eclipse/ : https://perfht.ml/2JAJtij
Comment 10•6 years ago
|
||
Those profiles are crazy! You're getting really poor compositing performance, but the time is almost exclusively spent within VerifyVersionInfoW, which really doesn't seem like useful work.
It's possible that the symbols are incorrect, but that seems really unlikely since the stack is multiple levels deep, and covers multiple binaries (ntdll.dll, and kernel32.dll) and forms a coherent chain.
It seems that either the Intel driver you have is calling this function way too often, or something to do with your Windows install is making the function much slower than expected.
I can't reproduce this on my machine (different intel chip, but same driver version), so the former seems unlikely.
I'm not sure what to do from here, it's going to be really hard to diagnose this until we find a way to reproduce the issue.
I'm going to remove this from the tracking bug (sorry!), since we're only tracking issues that affect NVIDIA at this stage.
No longer blocks: stage-wr-trains
Updated•6 years ago
|
Blocks: stage-wr-backlog
Reporter | ||
Comment 11•4 years ago
|
||
This is smooth now
Reporter | ||
Updated•4 years ago
|
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•