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

ConEmuC: Root process was alive less than 10 sec, ExitCode=0. #1773

Closed
kayzzen01 opened this issue May 14, 2018 · 22 comments
Closed

ConEmuC: Root process was alive less than 10 sec, ExitCode=0. #1773

kayzzen01 opened this issue May 14, 2018 · 22 comments

Comments

@kayzzen01
Copy link

I was using the cmder with bash and closed with using control + D after about 3 seconds, then the following displayed the following message:

ConEmuC: Root process was alive less than 10 sec, ExitCode = 0.

Would you like to know if this is a bug or just a message ?
Can you corrupt something in the cmder or ConEmu?

Thanks.

@jschneidereit
Copy link

I get the same error on windows 10 when trying to start any shell to do with powershell (bash works fine for me)

ConEmuC: Root process was alive less than 10 sec, ExitCode=0.

@Stanzilla
Copy link
Member

Reload the default tasks, and see if those work

@jschneidereit
Copy link

Same deal 😢

@Stanzilla
Copy link
Member

Can you post the content of the task you are running?

@jschneidereit
Copy link

Task Parameters: /icon "%CMDER_ROOT%\icons\cmder.ico"
Commands: PowerShell -ExecutionPolicy Bypass -NoLogo -NoProfile -NoExit
(Just the default powershell task)

FWIW I also tried deleting the task parameter and running only the command, but no dice

@Stanzilla
Copy link
Member

try PowerShell.exe. Also my default task is powershell.exe -new_console:d:%USERPROFILE%

@jschneidereit
Copy link

Tried both of those, no change

@Stanzilla
Copy link
Member

well is powershell on your path?

@jschneidereit
Copy link

from vanilla command prompt:

C:\Users\jschneidereit>echo %PATH%
C:\Program Files\Docker\Docker\Resources\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;

from bash in cmder:

jschneidereit@compy ~
λ which powershell
/c/WINDOWS/System32/WindowsPowerShell/v1.0/powershell

@Stanzilla
Copy link
Member

Really no idea then, can you try a nightly build? https://ci.appveyor.com/project/MartiUK/cmder/build/1.0.667-master/artifacts

@jschneidereit
Copy link

Nightly does the same thing 😂 at this point I'd point the blame at my laptop - but it's been freshly imaged.

I'll go back to older builds and try that now 😞

@kayzzen01
Copy link
Author

I asked in the ConEmu project and they informed me this:

@TeamSpen210
"This is a convenience feature. If you run a process and it quits before 10 seconds are up, ConEmum keeps the tab open until you press a key. That ensures if you run some program that ends quickly, you can still see the messages it produces. You can change this to be always/never/10 seconds only in the settings."

Maximus5/ConEmu#1556 (comment)

@ittayd
Copy link

ittayd commented Dec 10, 2018

not sure why you closed this. powershell crashes...

@daxgames
Copy link
Member

Probably because this is not a cmder issue.

@kayzzen01
Copy link
Author

According to TeamSpen210 this is a feature of convenience. I tried to reproduce the same error using the powershell and it did not occur.

@ittayd Can you tell me how to reproduce ?

@ittayd
Copy link

ittayd commented Dec 11, 2018

Well, obviously something in my environment that causes it. But I have no idea how to debug it.

@daxgames
Copy link
Member

@ittayd Questions:

  1. I assume Powershell works outside Cmder?
  2. Do Cmder Cmd and Bash sessions work?
  3. If 1 and 2 = Yes what are the contents of %cmder_root%\config\user_profile.ps1 and from Powershell the contents of the $profile file.
  4. Are there any *.ps1 files in %cmder_root%\config\profile.d

You could launch a Cmder Cmd session and run cmder_diag.cmd and post the output. This may give us enough of a picture of your environment to help. Make sure you look at the output and sanitize it before posting, it probably doesn't contain anything sensitive but just make sure.

@ittayd
Copy link

ittayd commented Dec 11, 2018 via email

@daxgames
Copy link
Member

@ittayd Glad you found the issue.

If you do not have %cmder_root%\config\user_profile.ps1 you are running an older version OR Powershell never got far enough in Cmder to actually create one for you. Now that you say it is working it should exist now.

@ittayd
Copy link

ittayd commented Dec 11, 2018 via email

@daxgames
Copy link
Member

@ittayd then something is still broken because it should self create. The diag file did not come through. I assume you attached it to an email.

@ittayd
Copy link

ittayd commented Dec 13, 2018

cmder_diag.zip

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

5 participants