Log window hangs on pasting wrong SHA-1 into commit log list when "working tree changes" are selected

What steps will reproduce the problem?

1. Copy the SHA-1 for a commit to the clipboard, but with an extra space at the end (copying from a browser will easily do that)
2. Focus on the commit log list in the log for a repository, and make sure you select the first line for "Working tree"
3. Hit Ctrl + V to paste the SHA-1 to jump to it

What is the expected output? What do you see instead?

Expected: Log jumps to the respective commit, or does nothing/beeps/shows a message if the SHA-1 can't be found.

Actual: TortoiseGitProc hangs indefinitely with one CPU core pegged to 100%, and needs to be killed.

What version of TortoiseGit and Git are you using? On what operating system?

TortoiseGit 2.12.0.0 (C:\Devel\TortoiseGit\bin)
git version 2.34.1.windows.1 (C:\Devel\Git\bin; C:\Devel\Git\mingw64; C:\Devel\Git\etc\gitconfig)
Microsoft Windows [Version 10.0.18363.1854] x64

Please provide any additional information below.

Actually pasting any SHA-1 that can't be found when starting from the "Working copy" first line of the log will hang it.