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

Hang on new Shells > Cmd console #623

Open
Danita opened this issue Apr 3, 2016 · 24 comments
Open

Hang on new Shells > Cmd console #623

Danita opened this issue Apr 3, 2016 · 24 comments

Comments

@Danita
Copy link

Danita commented Apr 3, 2016

Versions

ConEmu build: 150813g x64
OS version: Windows 7/x64
Used shell version (Far Manager, git-bash, cmd, powershell, cygwin, whatever): cmd

Problem description

When opening a new Cmd shell, ConEmu hangs indefinitely on a new empty window. When I press CTRL+C, I get the "Finish batch process" prompt. I investigated a little and I found the culprit on CmdInit.cmd line 8:

cmd /d /c ver | "%windir%\system32\find.exe" "Windows"

It's the find.exe which just hangs the batch process. If I remove this line (or even just remove everything from the pipe) it works OK.

Steps to reproduce

  1. Configure ConEmu to use different windows instead of tabs
  2. Open a new Cmd shell from the little [+] in the status bar

Actual results

ConEmu opens a new empty window but prompt won't appear until Ctrl+C is pressed.

Expected results

ConEmu should open a new fully functional Cmd window

@Maximus5
Copy link
Owner

Maximus5 commented Apr 3, 2016

@Danita
Copy link
Author

Danita commented Apr 3, 2016

Sorry, editing.

@Maximus5
Copy link
Owner

Maximus5 commented Apr 3, 2016

If you are using old build, there is big chance that your problem was fixed already. Don’t waste your time reporting problems of Old Builds. Why not to update?

@vensko
Copy link

vensko commented Dec 12, 2016

find.exe in Windows 7 x64 hangs if cmd codepage is set to utf-8, can be chcp utf-8 in Settings (if a batch file is running in ConEmu), registry key HKEY_CURRENT_USER\Console\CodePage or right in a batch file.

@Maximus5
Copy link
Owner

I need process dump of "hanged" find.exe
https://conemu.github.io/en/MemoryDump.html

@hsmyers
Copy link

hsmyers commented Mar 6, 2017

It is now March of 2017 and this problem persists. And before someone 'demands' a memory dump, I would point out that the numbers displayed in ConEmu, both display line and in the dialog are wrong causing the debug request to error out.

I have not experimented with the .cmd file as yet.

Hugh S, Myers

@Maximus5
Copy link
Owner

Maximus5 commented Mar 6, 2017

Yep, March 2017 and there is still no answer to my "demand".

both display line and in the dialog are wrong causing the debug request to error out.

What?

@hsmyers
Copy link

hsmyers commented Mar 7, 2017 via email

@libichong
Copy link

libichong commented Mar 15, 2017

@Maximus5 I met the same issue when i run the command "es.exe" which is the client application of windows everything. You can try it here https://www.voidtools.com/ES-1.1.0.7.zip and you also need to install everthing. It can repro in all my machines.

@hsmyers
Copy link

hsmyers commented Mar 15, 2017 via email

@libichong
Copy link

Apologized for the misguided steps. You also need to download https://www.voidtools.com/Everything-1.3.4.686.x86.Multilingual-Setup.exe

Because I tried in my Command Prompt and native Powershell. es.exe can work but conemu will get stuck and no response. I have to break the process

@hsmyers
Copy link

hsmyers commented Mar 15, 2017 via email

@libichong
Copy link

The execution will go to the following code path and I saw the following comments.

// 120603. В принципе, это штатная ситуация, если ни одного запроса на
// подключение не было. Но было зафиксировано странное зависание клиента
// при попытке подключения к пайпу с mn_MaxCount=1. Пайп вроде был живой
// и свободный, но тем не менее, на клиенте все время возвращалась
// ошибка ERROR_PIPE_BUSY.
//
//_ASSERTEX((nDuration <= nMaxConnectDuration) && "Unknown problem, waiting for connection");

@hsmyers
Copy link

hsmyers commented Mar 15, 2017 via email

@Maximus5
Copy link
Owner

There is still neither stack nor process dump.

@Maximus5
Copy link
Owner

And I don't see any problems with es.exe on my PC

@hsmyers
Copy link

hsmyers commented Mar 15, 2017 via email

@Maximus5
Copy link
Owner

First of all, the issue was created about find.exe hang. And there were no aswers for my requests.

@hsmyers what process hang do you mean?

@libichong talks about es.exe which is definitely absolutely different than find.exe and I suppose there may be different problems.

Anyway, if one say "process hangs", it's supposed to be they know what process hangs. There are plenty much ways to know PIDs of processes. ProcessExplorer is easiest of them. And I said many times what information I need to understand the problem.

  • The description. What do you do and what hangs.
  • MemoryDumps of processes you see in the ProcessExplorer.
  • Screenshots (of ConEmu window and process tree from ProcessExplorer) would be helpful too

@hsmyers
Copy link

hsmyers commented Mar 15, 2017 via email

@hsmyers
Copy link

hsmyers commented Mar 15, 2017 via email

@libichong
Copy link

Hi guys, please ignore my previous post. It's NOT conemu issue.

The issue: I started Everything with normal privilege. The default startup newly-created console is PowerShell with administrator privilege. So es.exe in conemu will be stuck and I started PowerShell with normal privilege works well. It made me feel that it was conemu stuck issue.

Solution: start Eveything and es.exe with the same privilege.

@ghost
Copy link

ghost commented Jul 24, 2017

I use portable version on windows 8/10 no problemo
when switch back to normal OS like windows 7 i get this error
__
I just start using power shell because its random sometimes its hange like 4 times in row

  • try to create script on another shell with kill process by name i.e node.exe but its process hang too
  • maybe this is emet issue but i don't see conemu width run ement flag ?
  • hang when type php.exe script.php or node script.js or even ping
  • only help kill process by task menage
  • hanged script are run but do nothing
  • cant kill by ctrl + c
  • somtimes when run conemu its not showing console on some tabs
  • can't replicated on windwso 7 Vm
  • somtimes i see find.exe but last hang don't have this process

@Maximus5 - what is your email i will be send you my dump form process explorer

image

This happens for me even in console2 sometimes less often

@Maximus5
Copy link
Owner

@usrnamatnull my e-mail publicly available in many places, in account properties for example.

"Undefined" means ConEmu doesn't force cmd to change output mode.
http://conemu.github.io/en/SettingsComspec.html#choose-preferred-command-processor-platform-bits

@densom
Copy link

densom commented Oct 31, 2017

I have noticed the crash is coming from the cmd /d /c ver | "%windir%\system32\find.exe" "Windows" line as well. However, it is the cmd that is causing the error on my side. For example, to reproduce:

  1. Launch ConEMU into a standard prompt (clearing any error messages that appear)

  2. type cmd at the prompt and press enter

  3. type exit to exit from the shell that was launched

Notice the same error occurs as when you launch.

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

No branches or pull requests

6 participants