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

Having ConEmu visible with git-bash causes dwm.exe to use significant CPU time #830

Closed
hjohn opened this issue Aug 15, 2016 · 8 comments
Closed

Comments

@hjohn
Copy link

@hjohn hjohn commented Aug 15, 2016

Using the most recent version 160724 (but effect is also present in versions a year older).

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

Problem description

With ConEmu window visible, or behind another window, or maximized, Task Manager shows CPU of dwm.exe to be 10%-20% of one core.

As soon as ConEmu window is minimized, it drops to 0%.

This is with ConEmu window doing nothing, single tab open, waiting at prompt.

If I close git-bash, and open a cmd tab instead, this does not happen.

Steps to reproduce

  1. Start ConEmu
  2. Open git-bash tab
  3. Check Task Manager while window is not minimized vs minimized

Actual results

High CPU use of dwm.exe while window is not minimized

Expected results

No CPU use of dwm.exe

@hjohn
Copy link
Author

@hjohn hjohn commented Aug 15, 2016

I realize this might be an issue with git-bash itself, but this only happens when integrated with ConEmu, not when using git-bash using standard windows console, so it could be either...

@Maximus5
Copy link
Owner

@Maximus5 Maximus5 commented Aug 15, 2016

Using ChildGui with enabled transparency usually raises dwm utilization.
I consider this is not a ConEmu problem.

@hjohn
Copy link
Author

@hjohn hjohn commented Aug 15, 2016

Transparency option is not active in my case though, I will try investigate further in that direction
On Aug 15, 2016 6:26 PM, Maximus5 notifications@github.com wrote:Using ChildGui with enabled transparency usually raises dwm utilization.
I consider this is not a ConEmu problem.

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

@tni
Copy link

@tni tni commented Sep 19, 2016

I'm not sure if it's the same issue, but I'm seeing high dwm CPU usage when the active tab has been renamed, e.g. via "-new_console:t:VS2015x64". Switching to a tab with a default name (no new_console parameter) reduces the CPU usage.

The same thing happens when I rename a tab via the context menu, CPU usage goes up. When I set the default name (using a blank name), CPU usage goes down.

Transparency is disabled.

@Maximus5
Copy link
Owner

@Maximus5 Maximus5 commented Sep 19, 2016

@tni What OS you are using? Versions? LogFiles with high CPU consumption?

@tni
Copy link

@tni tni commented Sep 19, 2016

Win7 x64 Ultimate. Looking at the logfiles, SetTitle is called every 10 milliseconds when a tab with custom title is active:

0:48:31.370 SetTitle: hWnd=x8410fc Title=renamed tab
0:48:31.381 SetTitle: hWnd=x8410fc Title=renamed tab
0:48:31.392 SetTitle: hWnd=x8410fc Title=renamed tab
0:48:31.403 SetTitle: hWnd=x8410fc Title=renamed tab
0:48:31.413 SetTitle: hWnd=x8410fc Title=renamed tab
0:48:31.424 SetTitle: hWnd=x8410fc Title=renamed tab
...

ConEmu-con-66128.log.txt
ConEmu-con-66352.log.txt
ConEmu-srv-66128.log.txt
ConEmu-srv-66352.log.txt
ConEmu-gui-66448.log.txt

@tni
Copy link

@tni tni commented Sep 20, 2016

BTW, this already occurs with ConEmu from 1 year ago.

I hacked the GIT version of ConEmu and removed a bunch of SetTitle stuff. That brings down the CPU usage to about the same level as a non-renamed tab.

@tni
Copy link

@tni tni commented Nov 10, 2016

Thanks - your fix is working for me.

@Maximus5 Maximus5 closed this Nov 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.