When a large file (~300 MB was enough to cause this for me) is opened, I get a warning that the file has not been loaded due to the file being large. Even if I don’t click “open anyway”, my ssh connection becomes unusably slow, I can’t open new terminals or files, the only solution is killing the remote server and reloading.
Steps to Reproduce
In a Remote SSH session, click on a large file (~300 MB) in the file explorer. This has caused issues consistently
Expected Behavior
Opening the file should not cause my entire remote ssh session to die if I don’t select “open anyway”
It looks like this is related to how large files are handled in a Remote SSH session. Even without clicking “Open Anyway”, some kind of preloading seems to happen, and it ends up freezing the connection.
A couple of questions to help us debug:
What’s the exact file size, is it around 300 MB or more or less?
How much RAM does the remote server have?
Does this happen with all large files, or only a specific type like JSON, log, CSV?
For now, a workaround is to avoid clicking on files in the file explorer if you know they’re large.
I’ll pass this to the team. It’s on our radar, and any extra details will help us prioritize it.
same problem. when i use cursor remote ssh to open a big file, the remote ssh will try to download it fully(i guess) even if i did not click “open anyway“, i see the bottom right “SSH Traffic Monitor“ download traffic is increasing when i open a big file even if i just click the file and close the file’s tab at moment, it will occupy the normal operating’s traffic so that all the file operate will stuck util the big file is download to local fully. the version i not met this error is “CursorSetup-x64-2.0.34“ in windows, but newest version “CursorSetup-x64-2.5.25“ and older “CursorUserSetup-x64-1.4.5“ has this problem
every file size larger than (network bandwidth between localhost and remote server * 1-20 seconds ) will cause a little stuck, the bigger, the stuck persist time longger.
the remote server‘s RAM more than 128GB
json/jsonl , log , file like nohup.out both have same problem