After a few commands, it just hangs and doesn't work anymore. I've tried running as user and as administrator, no difference.
I'm using build 144
There seems to be some issue in message passing from CMessageLoop to ConsoleHandler::MonitorThread. I am able to repro it consistently with:
1. Open console version of vim with a long file
2. Keep the down arrow key pressed for few seconds
3. Console2 doesn't respond, however other tabs respond
This sends bunch of WMKEYDOWN events to the app, but they seem to get lost in the thread's message queue. MonitorThread enters an infinite loop waiting for events to occur.
Let me know if a dump or callstack can help.
I can confirm that this is a issue on Windows 7. When trying to run Git within Console2, I can only issue a few commands before it freezes up. The other tabs remain functional.
Is it possible for you to debug Console?
Yes I can debug console. Please let me know if I can provide any information.
If you guys are running builds before b145, please try b145 (that one partially fixes the Win7 lockup problem)
Kirill has also provided a development build on his site, you can try that as well...
Just for completion, I (the original poster of this item) should note here that this issue appears to be thoroughly solved in Kirill's V146.1.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.