node-red: Blank window in Chrome after returning to NR
What are the steps to reproduce?
I often leave NodeRed open in the browser as a tab. After upgrading to 1.1.0, returning to a previously opened browser tab yields a completely blank screen. There does seem to be some kind of timeout related to this - e.g., if I wait 5 seconds, this won’t happen, but it will happen after ~30 minutes.
If I pop open developer tools – this seems to fix it and it will start working normally again.
What happens?
Blank screen
What do you expect to happen?
See my nodes (as with the previous version). I have 151 nodes so the start up is a bit slower now with some changes in the interface. Is it timing something out?
Please tell us about your environment:
- Node-RED version: 1.1.0
- Node.js version: 10.21.0
- npm version: 6.14.5
- Platform/OS: macOS (NR is running on Pi, but I suspect not related)
- Browser: Chrome Version 83.0.4103.106 (Official Build) (64-bit)
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 26 (21 by maintainers)
Commits related to this issue
- Add RED.view.DEBUG_SYNC_REDRAW to disable requestAnimationFrame References #2631 — committed to node-red/node-red by knolleary 4 years ago
Closing as there have been no more reports of issues since 1.1.1 was published.
For the upcoming 1.1.1 release I’ve made a couple changes.
I’ve slightly changed the logic around our use of
requestAnimationFrameto avoid it being overloaded. It’s a bit of a theoretical fix - would be interested to hear if it helps.You can disable our use of requestAnimationFrame by opening the devtools window and entering:
That will only apply for the current session - reloading the page will revert back. But it would be great if anyone still experiences the issue with 1.1.1 could try setting that value and then see if you can recreate. That would help rule in/out the use of requestAnimationFrame as the root cause here.
1.1.1 will be released this week.