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

ConEmu is using 30% CPU on an i5 quad core 3.2ghz when idling with a few terminals open #1735

Open
nickjj opened this Issue Oct 16, 2018 · 14 comments

Comments

Projects
None yet
2 participants
@nickjj

nickjj commented Oct 16, 2018

Versions

ConEmu build: 180626 (tried both x32 and x64)
OS version: Windows 10 Pro 18.09 (OS build 17763.55 stable channel)
Used shell version: WSL and PowerShell (just standard Bash with WSL, no fancy terminals or anything)

Problem description

I had a WSL terminal open and split into 3 windows and then had 2 additional WSL terminals open and I noticed with nothing else opened or running my CPU load was about 30%-35% on an i5 3.20ghz.

After closing every ConEmu window my CPU usage immediately dropped to about 3-5%. Those 5 WSLx terminal sessions were doing no work.

On my machine if I open up a WSL terminal and split it into 5 windows and then open 9 additional separate WSL terminals then my idle CPU is about 50%, so it's not just hard capping at about 30%. It appears to climb up as you open more ConEmu driven sessions.

I repeated the same test using the built in bash.exe from Windows instead of ConEmu and my CPU usage with 10 of those open was about 3-5% which is the same as not having any open. PowerShell without ConEmu had the same results of being at about 3-5%.

Steps to reproduce

  1. Open a bunch of WSL terminals (or PowerShell has the same effect) using ConEmu
  2. Hit CTRL + Shift+ ESC to bring up the task manager and goto the performance tab
  3. Look at the CPU usage percent
  4. Close all ConEmu terminals
  5. Look at the CPU usage percent
  6. (Optional) repeat the above but opening up double or triple the amount of ConEmu terminal sessions

Actual results

A lot more CPU usage than normal.

Expected results

A lot less CPU usage.

Additional files

I'm not using transparency or anything fancy. Tab bar is set to "don't show" as well.

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Oct 16, 2018

Have you read docs?
CPU and I/O consumption

@nickjj

This comment has been minimized.

nickjj commented Oct 16, 2018

The docs mention 64bit exclusively but this problem happens on both 32bit and 64bit.

Turning both of those options on helps a little but not much. It still uses around 15-20% instead of 30-35%.

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Oct 16, 2018

It doesn't mention 64 bit exclusively. Do you know the meaning of square brackets?

PTY API is not supported yet, continuous scanning of conhost surface may produce consumption.
Moreover, the conhost itself may produce consumption too.

@nickjj

This comment has been minimized.

nickjj commented Oct 16, 2018

Is there anything I can do in the settings to further reduce CPU usage? I don't really care what things look like, I just want to be able to open a lot of terminals without half of my CPU being used.

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Oct 16, 2018

Try to run ConEmu64.exe -basic {bash}.

@nickjj

This comment has been minimized.

nickjj commented Oct 16, 2018

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Oct 16, 2018

@nickjj

This comment has been minimized.

nickjj commented Oct 16, 2018

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Oct 16, 2018

Sorry

ConEmu64.exe -basic -run {bash}
@nickjj

This comment has been minimized.

nickjj commented Oct 16, 2018

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Oct 17, 2018

By the way, you issue doesn't show were this utilization occurs.
I recommend ProcessExplorer to check.

@nickjj

This comment has been minimized.

nickjj commented Oct 17, 2018

Good idea. Before I install that, are you able to reproduce the same problem on your end with comparable unexpected CPU usage?

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Oct 18, 2018

I've never seen such large utilisation in rest (it's usually lower than a percent on my home PC).
When you run in ConEmu something producing massive output to the console, utilization augmentation is expected.

I can't test your exact build of Windows 10.

@nickjj

This comment has been minimized.

nickjj commented Oct 18, 2018

Yeah, in this case it's just idling.

In this screenshot all I did was open 10x ConEmu windows into a vanilla WSL / Bash prompt.

I'm not sure what you would like to see but I ran ProcessExplorer with DLLs shown as per your guide. I also sorted things so processes using the most CPU are loaded on the bottom.

conemu-cpu

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