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

Processes dying due to lack of memory? #1106

Closed
tul opened this issue Sep 29, 2016 · 7 comments
Closed

Processes dying due to lack of memory? #1106

tul opened this issue Sep 29, 2016 · 7 comments
Labels
👆 Git Upstream issue in Git for Windows.

Comments

@tul
Copy link

tul commented Sep 29, 2016

Hi there,

Using cmder (ConEmu 160710 [64]) version 1.3.0 on Windows 10, I often get into a state where I SSH into a remote server, and then whatever command I run on the remote server, for example, vi or less, will cause the SSH session to abruptly drop with the message:

0 [main] ssh 428204 C:\cmder\vendor\git-for-windows\usr\bin\ssh.exe: *** fatal error - cmalloc would have returned NULL

Once this starts happening, I have to shut down cmder and start a new session, in which SSH will work as normal.

The Windows Task Manager shows Consule Emulator (x64) is taking only 46.5 MB. There is plenty of free memory both on the local Windows box and the remote server.

If there is any more information I can provide I will happily assist.

Thx!

@MartiUK MartiUK added the 👆 Git Upstream issue in Git for Windows. label Sep 29, 2016
@MartiUK
Copy link
Member

MartiUK commented Sep 29, 2016

Have a look at this issue: git-for-windows/git#356 (comment), unfortunately it's closed without an answer but the reporter mentioned reducing the size of the screen buffer.

@tul
Copy link
Author

tul commented Sep 29, 2016

Thanks, I had set it to 32767 and I was wondering if that could be involved somehow. I will lower it and see how I get on.

@MartiUK MartiUK closed this as completed Oct 9, 2016
@morfien101
Copy link

I can confirm that lowering the screen buffer has also fixed my issue.

I had it set to 32000 and dropped it to 10000.
I must admit that I did not experiment on numbers but this worked for me once I opened a new console.

Build: ConEmu161206 if it helps.

@sryze
Copy link

sryze commented Aug 2, 2018

I changed the screen buffer size to 10000 lines but still have this issue. Is there another solution?

Where do you change the buffer, is it this setting?

buffer

@CIPop
Copy link

CIPop commented Aug 25, 2018

+1 I have set the long console output to 10k and still have the issue. If I need to drop it to 1k then cmder is useless.

Doing a cls made things work w/o restarting cmder. (Idea from here: git-for-windows/git#356 (comment))

@vekien
Copy link

vekien commented Nov 26, 2018

I have this issue ALL THE TIME and it's so frustrating, it happens everytime i use nano and it's always random, i have 32gb of memory so I'm defaintly not running out, even on a 200 line screen buffer it happens, i've tried so many values, it's practically a useless option.

Can this be looked into? It happens about 15 times a day. Only with cmder.

@7dir
Copy link

7dir commented Oct 4, 2019

run As Administrator in new windows works

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

No branches or pull requests

7 participants