Unknown GHCI Issue Causing Lag After Ctrl C on (at least) Windows

Sorry about this, but this could be a lot easier if I showed my code, but I'm a bit shy as the code is "s-code".

Summary

If you run either code that takes a long time to finish, or parallelized code that takes a long time to finish, Ctrl+C on Windows 10 causes the terminal to start behaving slowly, with substantial lag between key presses and terminal responses. POSIX emulation, not WinIO. This resolves after GHCI receives a :q command and is restarted.

Edit: using slow_fib from https://wiki.haskell.org/Memoization doesn't reproduce this bug.

Moreover, a further bug is noted wherein Ctrl+C has to be pressed at least twice to exit. Further edit: cannot reproduce Ctrl+C bug.

This is consequently a bug with code that relies on Eval parallelization.

Steps to reproduce

I'll show my "s-code" if this can't be reproduced.

Expected behavior

Environment

GHC version used: 9.2.4

Optional:

Operating System: Win10
System Architecture: x64

Edited Aug 29, 2022 by liam zhu

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information