Stuck on an issue?
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.
Setting a property currentPageNo is working too slow
See original GitHub issueHello! I have an unpleasant issue related to performance in case I set currentPageNo property. It takes from 6 to 30 sec.
- browser: Chrome
- browser version: 70.0.3538.77
- surveyjs platform: jquery
- surveyjs version: 1.0.52
Why does it happen?
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (9 by maintainers)
Top Results From Across the Web
JavaScript Updating CSS custom properties slower than using ...
So I went a bit further and changed my code so that I directly write the CSS custom property to the element via...
Read more >Get-VirtualDirectory run slowly - Exchange - Microsoft Learn
This issue occurs because the cmdlet makes calls to the Internet Information Services (IIS) metabase for the properties of the virtual directory ...
Read more >How to improve my website speed. My website is too slow ...
If you want to disable the slider, navigate to Theme options > Design > Property, Agent, Blog Lists Design section and set NO...
Read more >Slowing down to speed up | McKinsey & Company
Pace the speed of your work: Slow down to speed up. Trust that solutions are always available. Set the right attention and intention...
Read more >How to fix QGIS being extremely slow? - GIS Stack Exchange
If it works, try to compare both Profile folders by opening both of them using "Settings -> User Profiles -> Open Active Profile...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@stsiushkevich We’ve investigated the issue and made some improvements. You can check it in the nearest minor update. Most likely it will be released next tuesday.
Could you provide us with exact steps to reproduce the issue on our online demos or a link to a plunker illustrating the issue?