Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Out of memory-error #650

Open
finallynl opened this issue Dec 26, 2022 · 1 comment
Open

Out of memory-error #650

finallynl opened this issue Dec 26, 2022 · 1 comment

Comments

@finallynl
Copy link

finallynl commented Dec 26, 2022

Bug

I've two Windows 11 laptops, synced and all with the same setup. I do use Git-Ftp for a long time now, always works well.
I see a problem happening when using git ftp init so when I do upload a lot of files for first time. (no problem with git ftp push).

  1. On one laptop everything is fine when uploading / syncing with FTP.
  2. On the second laptop it gives an 'out of memory' error with git ftp init (so a lot of files)

It's the same FTP hosting, same credentials, same website and no problem with space there. So I think there must be something on my second machine

Git FTP

  • I am using 1.6.0 on both machines

What?

  • There probably must be a difference in the versions of software or so. But I don't know where to check. Can somebody give me any direction? Like Powershell? Git?
@rtharston
Copy link

Perhaps the different machines are running different versions of curl. You can check with curl --version.

Since curl 7.86.0 some errors our incorrectly reports as '(27) Out of memory' when there was actually a different error, so it may not actually be a memory problem. (See the last few comments on curl/curl#10130 for a discussion about this.)

I ran into the same issue that @kitsguru reported in issue #648, which was actually a problem with spaces in the path, but this out of memory error was presented instead. Perhaps that is what you are hitting as well?

Issue #633 reported that curl stopped accepting URLs with spaces in them, and there is an open PR to fix paths with spaces in them so curl will accept them.
(There is also a PR open in curl/curl#10414 that fixes the issue with wrongly reporting out of memory for other errors, which at least helps make the real issue clear.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants