PERF: CPU "leak" after opening and closing dropdown with *noink* attribute

[louisptremblay]

CPU goes up to 10% after one opening and closing a dropdown with noink attribute. Doesn't ever go back to normal after that. The more time you open and close, the higher the CPU raises, never going back down.

Easy to reproduce (the bug can be seen in the official demo page):

• Go to https://elements.polymer-project.org/elements/paper-dropdown-menu?view=demo:demo/index.html&active=paper-dropdown-menu
• Wait for the page to finish loading and close every other Chrome tabs.
• Observe that your Chrome CPU usage is very low (2-3%)
• Open and close the last dropdown a few times on the demo page (No Ripple, No Animations).
• CPU has gone significantly higher and is not going back down even after waiting a long time

Thank you!

[ghost]

Wow that's pretty bad! I see what you mean.

[ebidel]

Believe this is in paper-ripple, but draw is being called continuously without anything to draw:

cc @rictic @cdata

[cdata]

Looks like this might be a paper-ripple bug.

[ebidel]

ping @cdata

[Eymerich01]

No news about this issue? My application becomes unusable for CPU problem :( The only way to solve this is to put periodically _animating=false on any paper-ripple.