Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[BUG] checkIfDefined is doing nothing but wasting CPU
See original GitHub issueDescribe the bug
The current implementation can and is endlessly looping so long the elements are not defined which in some cases won’t be and due to the logic used in this function it will somehow use noticeable (on low-medium spec CPU) CPU Utilization.
Steps to reproduce
- Go to mail.google.com
- Open performance tab in Dev tools
- Get a fresh performance
ctrl +eafter the page has been fully loaded. - See that even that checkIfDefined is still being called in a animationFrame alongside checkForUpdate(expected)
Expected behavior
Not using CPU or some other implementation to prevent this, not even sure what :defined has to do with Shadow DOM’s.
Actual behavior
It’s using CPU utilization even in idle when not needed
System Information:
- OS: Windows 10
- Browser: Vivaldi(3.4.2066.76)
- Dark Reader version: 4.9.21
Additional context
More info about this https://github.com/darkreader/darkreader/issues/3811#issuecomment-712695274
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Lot of work! Thank you!
@ddnexus #4005