Closed JVimes closed 1 year ago
The repro seems to happen more on some repos and not others. I wish I could post the repo I have that shows it the most (lags the most), but it's for work.
@JVimes please try disabling process search or in app content search in Settings -> Processes, or if you use these add this app to the ignore list.
Thank you much. Adding TortoiseGitProc
to the ignore list fixed it.
Do some apps just not play well with process search?
Thank you much. Adding
TortoiseGitProc
to the ignore list fixed it.Do some apps just not play well with process search?
Glad it helped. Yes Fluent Search uses Windows accessibility feature to do in app content search and some apps do not have good accessibility support.
Maybe a timeout would work as a failsafe? I'm assuming my unresponsive app caused an API call to not return for a long time since my window was totally frozen.
Maybe a timeout would work as a failsafe? I'm assuming my unresponsive app caused an API call to not return for a long time since my window was totally frozen.
I wish I could detect it, it's not even about timeout it's just Fluent Search call the accessibility api once, and since the software implementation does not handle it efficiently it may stuck in some cases. If I was able to detect it I would've ignored the software automatically.
Ah, gotcha. I think TortoiseGitProc is a safe candidate for default exclusion in the app, should you decide. Thank you again!
Describe the bug
While FluentSearch is running, TortoiseGit takes around 3-10 sec to become responsive when doing certain operations (often opening or closing a window).
To Reproduce
Expected behavior TortoiseGit is not unresponsive while FluentSearch is running.
Desktop (please complete the following information):