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

node.exe produce tons of errors #507

Closed
alex-fomin opened this Issue Jan 14, 2016 · 5 comments

Comments

Projects
None yet
2 participants
@alex-fomin

alex-fomin commented Jan 14, 2016

I'm using pm2 that causes many node.exe restarts and ConEmu spawns a lot of errors looks like:

---------------------------
ConEmuC, PID=1836
---------------------------
Attach to console app was requested, but there is no console processes!

"C:\Program Files\ConEmu\ConEmu\ConEmuC64.exe"  /ATTACH /PID=14388
---------------------------
OK   
---------------------------

I turned off the default term option - but it doesn't help.

@Maximus5

This comment has been minimized.

Show comment
Hide comment
@Maximus5

Maximus5 Jan 14, 2016

Owner

It's not a DefTerm. It's an Autorun, which is registered on ComSpec settings page.
And you have not specified the build! Why?

Owner

Maximus5 commented Jan 14, 2016

It's not a DefTerm. It's an Autorun, which is registered on ComSpec settings page.
And you have not specified the build! Why?

@alex-fomin

This comment has been minimized.

Show comment
Hide comment
@alex-fomin

alex-fomin Jan 14, 2016

Sorry, the version is 160111 alpha.
I've cleared 'Automatic attach of cmd & Tcc/Le to ConEmu' - the error is disappeared, but now all nodejs.exe processes are started in a console window and then quickly hide away.

alex-fomin commented Jan 14, 2016

Sorry, the version is 160111 alpha.
I've cleared 'Automatic attach of cmd & Tcc/Le to ConEmu' - the error is disappeared, but now all nodejs.exe processes are started in a console window and then quickly hide away.

@Maximus5

This comment has been minimized.

Show comment
Hide comment
@Maximus5

Maximus5 Jan 14, 2016

Owner

So, what do you want from ConEmu?

Owner

Maximus5 commented Jan 14, 2016

So, what do you want from ConEmu?

@alex-fomin

This comment has been minimized.

Show comment
Hide comment
@alex-fomin

alex-fomin Jan 15, 2016

Ok, after uninstaling conemu nodejs.exe are still spawning its console windows, so it is not an issue of ConEmu. Still, tons of always-on-top windows with errors from ConEmu is not so good.

alex-fomin commented Jan 15, 2016

Ok, after uninstaling conemu nodejs.exe are still spawning its console windows, so it is not an issue of ConEmu. Still, tons of always-on-top windows with errors from ConEmu is not so good.

@alex-fomin alex-fomin closed this Jan 15, 2016

@Maximus5

This comment has been minimized.

Show comment
Hide comment
@Maximus5

Maximus5 Jan 15, 2016

Owner

If anyone produces tons of processes, how do you imagine ConEmu may limit this tons to one process? It's not a ConEmu problem at all.

Moreover, mentioned ComSpec autorun integration is obsolete and not generally recommended. It may work, but only with cmd.exe shell.

Owner

Maximus5 commented Jan 15, 2016

If anyone produces tons of processes, how do you imagine ConEmu may limit this tons to one process? It's not a ConEmu problem at all.

Moreover, mentioned ComSpec autorun integration is obsolete and not generally recommended. It may work, but only with cmd.exe shell.

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