Comfy-Org / Comfy-Org/ComfyUI_frontend
node2.0 does not respect viewport fps but noodle link does so link and node window not sync causing mismatch, lag behind
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 699
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 490
Description
### Prerequisites
- [x] I am running the latest version of ComfyUI
- [x] I have custom nodes enabled
### What happened?
set viewport fps to 1 and pan screen. node 2.0 and 1.0 behave differently.
strangely setting maximum fps to 0 fixes desync link rendering issue.
### Steps to Reproduce
1.
2.
3.
### How is this affecting you?
Crashes ComfyUI completely
### ComfyUI Frontend Version
1.47.11
### Browser
Chrome/Chromium
### Console Errors
```javascript
at 1 viewport fps node 2.0 node window is snappy but node 1.o is very slow
```
### Logs
```shell
```
### Additional Context
_No response_
Contributor guide
Research direction
Start by reproducing the issue in Chrome/Chromium with viewport FPS set to 1 while panning, comparing node 1.0, node 2.0, and noodle-link rendering. Investigate the frontend rendering path responsible for viewport frame limits; done means node and link windows remain synchronized without lag or a ComfyUI crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100