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

ConEmu shows assertion when terminating SSH session in stermc #620

Open
sa1nt opened this Issue Apr 2, 2016 · 6 comments

Comments

Projects
None yet
2 participants
@sa1nt

sa1nt commented Apr 2, 2016

stermc.exe is a part of Bitvise SSH Client

I'm launching it using ConEmu task, which is defined like this:

stermc -profile="C:\path\to\bitvise\profile.bscp" -new_console:t:"Console Title"

And when I type exit or Ctrl + D in the SSH session, ConEmu crashes. I couldn't attach the dump, that appeared in the ConEmuTrap folder on my desktop, here in GitHub, so here's a link to it on my Dropbox

Here's a copy of the SysInfo window in ConEmu:

ConEmu 160329 [64] Startup Info
  OsVer: 10.0.10586.x64, Product: 1, SP: 0.0, Suite: 0x100, SM_SERVERR2: 0
  CSDVersion: , ReactOS: 0 (), Rsrv: 0
  DBCS: 0, WINE: 0, PE: 0, Remote: 0, ACP: 1252, OEMCP: 437, Admin: 0
  AppID: 49922b4d6ae2ce22bcf871b666573d5f::161
  Desktop: `Winsta0\Default`, SessionId: 1, ConsoleSessionId: 1
  Title: `C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ConEmu\ConEmu (x64).lnk`
  Size: {0,0},{0,0}
  Flags: 0x00000801, ShowWindow: 1, ConHWnd: 0x00000000
  char: 1, short: 2, int: 4, long: 4, u64: 8
  Handles: 0x00000000, 0x00000000, 0x00000000
Current PID: 7088, TID: 10284
Active HKL: 0x0000000004090409
GetKeyboardLayoutList: 0x0000000004090409 0x0000000004190419 0xFFFFFFFFF0150426
CmdLine: "C:\Program Files\ConEmu\ConEmu64.exe" 
ExecMod: C:\Program Files\ConEmu\ConEmu64.exe
WorkDir: C:\Program Files\ConEmu
PathEnv: C:\Python27\Lib\site-packages\PyQt4;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Bitvise SSH Client;C:\Program Files\MATLAB\MATLAB Production Server\R2015a\runtime\win64;C:\Program Files\MATLAB\MATLAB Production Server\R2015a\bin;C:\Program Files\MATLAB\MATLAB Production Server\R2015a\polyspace\bin;C:\Python27;C:\Python27\DLLs;C:\Python27\Scripts;C:\Python27\Lib\site-packages\vtk;C:\Python27\gnuplot\binary;C:\Python27\Lib\site-packages\osgeo;C:\Program Files (x86)\pythonxy\SciTE-3.5.1-4;C:\Program Files (x86)\pythonxy\gettext\bin;C:\ProgramData\chocolatey\bin;C:\Program Files (x86)\Skype\Phone\;C:\Program Files\Calibre2\;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;C:\OCamlPro\OCPWin\wrappers;C:\OCamlPro\OCPWin\4.02.1+ocp1-full-mingw64-20160113\bin;C:\Program Files\Java\jdk1.8.0_66\bin;C:\Sysinternals;C:\ProgramData\chocolatey\lib\gradle\tools\gradle-2.2.1\bin\;E:\Users\sa1nt\AppData\Local\atom\bin;C:\Program Files (x86)\Microsoft SDKs\F#\4.0\Framework\v4.0
ConFont: 0  Lucida Console  00  Consolas
CMD's AutoRuns:
  HKCU: "C:\Program Files (x86)\clink\0.4.5\clink" inject --profile "~\clink"
Foreground: x01060790 {-8,-8}-{1374,746} 'VirtualConsoleClass' - cmd
MouseCursor: {897,425} MouseMonitor: 00010001 StartMonitor: 00000000
Display: bpp=32, planes=1, align=1, vrefr=60, shade=x00000000, rast=x00007E99, dpi=96x96, per-mon-dpi=1
Monitors (dpi: WholeDesktop, Effective, Angular, RAW):
  00010001: {0,0}-{1366,768} (1366x768), Working: {0,0}-{1366,738} (1366x738), dpi: {96,96};{96,96};{89,89};{125,125} `\\.\DISPLAY1` <<== Primary
Modules:
  00007FF70C270000-00007FF70C4E6FFF   277000 C:\Program Files\ConEmu\ConEmu64.exe
  00007FF822430000-00007FF8225F0FFF   1C1000 C:\Windows\SYSTEM32\ntdll.dll
  00007FF820440000-00007FF8204ECFFF    AD000 C:\Windows\system32\KERNEL32.DLL
  00007FF81F1E0000-00007FF81F3C7FFF   1E8000 C:\Windows\system32\KERNELBASE.dll
  00007FF822180000-00007FF8222D5FFF   156000 C:\Windows\system32\USER32.dll
  00007FF821BF0000-00007FF821D75FFF   186000 C:\Windows\system32\GDI32.dll
  00007FF822380000-00007FF822426FFF    A7000 C:\Windows\system32\ADVAPI32.dll
  00007FF8222E0000-00007FF82237CFFF    9D000 C:\Windows\system32\msvcrt.dll
  00007FF81FF90000-00007FF81FFEAFFF    5B000 C:\Windows\system32\sechost.dll
  00007FF821D80000-00007FF821E9BFFF   11C000 C:\Windows\system32\RPCRT4.dll
  00007FF820690000-00007FF821BEBFFF  155C000 C:\Windows\system32\SHELL32.dll
  00007FF81F7E0000-00007FF81F822FFF    43000 C:\Windows\system32\cfgmgr32.dll
  00007FF81EB90000-00007FF81F1D4FFF   645000 C:\Windows\system32\windows.storage.dll
  00007FF81F950000-00007FF81FBCCFFF   27D000 C:\Windows\system32\combase.dll
  00007FF81F650000-00007FF81F6B9FFF    6A000 C:\Windows\system32\bcryptPrimitives.dll
  00007FF820630000-00007FF820681FFF    52000 C:\Windows\system32\shlwapi.dll
  00007FF81EA50000-00007FF81EA5EFFF     F000 C:\Windows\system32\kernel.appcore.dll
  00007FF81F720000-00007FF81F7D4FFF    B5000 C:\Windows\system32\shcore.dll
  00007FF81EA60000-00007FF81EAAAFFF    4B000 C:\Windows\system32\powrprof.dll
  00007FF81EAB0000-00007FF81EAC3FFF    14000 C:\Windows\system32\profapi.dll
  00007FF822070000-00007FF82217AFFF   10B000 C:\Windows\system32\COMDLG32.dll
  00007FF81EAE0000-00007FF81EB65FFF    86000 C:\Windows\system32\FirewallAPI.dll
  00007FF81EB70000-00007FF81EB86FFF    17000 C:\Windows\system32\NETAPI32.dll
  00007FF821EB0000-00007FF821FF2FFF   143000 C:\Windows\system32\ole32.dll
  00007FF8204F0000-00007FF8205B0FFF    C1000 C:\Windows\system32\OLEAUT32.dll
  00007FF815530000-00007FF815539FFF     A000 C:\Windows\SYSTEM32\VERSION.dll
  00007FF814570000-00007FF8147E3FFF   274000 C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10586.0_none_8c15ae12515e1c22\COMCTL32.dll
  00007FF81CAE0000-00007FF81CB02FFF    23000 C:\Windows\SYSTEM32\WINMM.dll
  00007FF81CA60000-00007FF81CA8BFFF    2C000 C:\Windows\SYSTEM32\WINMMBASE.dll
  00007FF808BC0000-00007FF808BCBFFF     C000 C:\Windows\SYSTEM32\DAVHLPR.DLL
  00007FF81E550000-00007FF81E55AFFF     B000 C:\Windows\SYSTEM32\CRYPTBASE.DLL
  00007FF815C20000-00007FF815C38FFF    19000 C:\Windows\SYSTEM32\SAMCLI.DLL
  00007FF81DEC0000-00007FF81DECBFFF     C000 C:\Windows\SYSTEM32\NETUTILS.DLL
  00007FF81FDA0000-00007FF81FDDAFFF    3B000 C:\Windows\system32\IMM32.DLL
  00007FF81D7D0000-00007FF81D801FFF    32000 C:\Windows\SYSTEM32\fwbase.dll
  00007FF81D320000-00007FF81D3B5FFF    96000 C:\Windows\system32\uxtheme.dll
  00007FF81C5A0000-00007FF81C5C1FFF    22000 C:\Windows\SYSTEM32\dwmapi.dll
  00007FF81F830000-00007FF81F8D6FFF    A7000 C:\Windows\system32\clbcatq.dll
  00007FFFFB4A0000-00007FFFFB6DEFFF   23F000 C:\Windows\System32\msxml3.dll
  00007FF81E650000-00007FF81E678FFF    29000 C:\Windows\System32\bcrypt.dll
  00007FF81FC40000-00007FF81FD99FFF   15A000 C:\Windows\system32\MSCTF.dll
  00007FF8085F0000-00007FF808A8FFFF   4A0000 C:\Windows\system32\explorerframe.dll
  00007FF80A570000-00007FF80A5BFFFF    50000 C:\Windows\system32\edputil.dll
  0000000054610000-0000000054715FFF   106000 C:\Program Files\ConEmu\ConEmu\ConEmuCD64.dll
  00007FF808A90000-00007FF808AD9FFF    4A000 C:\Windows\system32\dataexchange.dll
  00007FF81C2F0000-00007FF81C597FFF   2A8000 C:\Windows\system32\d3d11.dll
  00007FF81CDB0000-00007FF81CE92FFF    E3000 C:\Windows\system32\dcomp.dll
  00007FF81C220000-00007FF81C2C2FFF    A3000 C:\Windows\system32\dxgi.dll
  00007FF81D570000-00007FF81D66FFFF   100000 C:\Windows\system32\twinapi.appcore.dll
  00007FF81C5D0000-00007FF81C755FFF   186000 C:\Windows\SYSTEM32\PROPSYS.dll
@Maximus5

This comment has been minimized.

Show comment
Hide comment
@Maximus5

Maximus5 Apr 2, 2016

Owner

Where are screenshots of the "crash message"?

Owner

Maximus5 commented Apr 2, 2016

Where are screenshots of the "crash message"?

@Maximus5

This comment has been minimized.

Show comment
Hide comment
@Maximus5

Maximus5 Apr 2, 2016

Owner
  1. Is that assertion (it's not a crash) reproducible?
  2. If so, please create https://conemu.github.io/en/LogFiles.html and screenshots, demonstrating the problem.
Owner

Maximus5 commented Apr 2, 2016

  1. Is that assertion (it's not a crash) reproducible?
  2. If so, please create https://conemu.github.io/en/LogFiles.html and screenshots, demonstrating the problem.
@sa1nt

This comment has been minimized.

Show comment
Hide comment
@sa1nt

sa1nt Apr 3, 2016

Yes, the easiest way to reproduce is to launch Midnight Commander during the SSH session. Can't say at the moment, what else seems to cause the assertion to fail.

Here's a zip with logs and screenshots, taken on ConEmu ver. 160329.
ConEmuLogs.zip

sa1nt commented Apr 3, 2016

Yes, the easiest way to reproduce is to launch Midnight Commander during the SSH session. Can't say at the moment, what else seems to cause the assertion to fail.

Here's a zip with logs and screenshots, taken on ConEmu ver. 160329.
ConEmuLogs.zip

@sa1nt sa1nt closed this Apr 3, 2016

@sa1nt sa1nt reopened this Apr 3, 2016

@sa1nt

This comment has been minimized.

Show comment
Hide comment
@sa1nt

sa1nt Apr 3, 2016

Also, after updating ConEmu to latest version 160403a the issue still remains.

sa1nt commented Apr 3, 2016

Also, after updating ConEmu to latest version 160403a the issue still remains.

@Maximus5 Maximus5 changed the title from ConEmu crashes when terminating SSH session in stermc to ConEmu shows assertion when terminating SSH session in stermc Apr 3, 2016

@Maximus5 Maximus5 added the assertion label Apr 3, 2016

@sa1nt

This comment has been minimized.

Show comment
Hide comment
@sa1nt

sa1nt May 20, 2016

Sorry for late response, but apparently that commit you made didn't really fix the problem.

I cannot recall the precise ConEmu version when this changed, but on ver. 160515 [64] {Preview} the situation is following.

When I type Ctrl+D or exit in the stermc SSH console and I had used Midnight Commander during this session, then CPU usage jumps to 100% and the machine completely stops responding. This, as far as I've found, may be "resolved" only with a hard reset of the PC. I have tried to wait it over, but after 30 minutes nothing's changed, so I still had to hard reset the PC.
ConEmu crash dump doesn't appear after this.

When I type Ctrl+D or exit in the stermc SSH console and Midnight Commander has not been launched during the session, everything's fine.

Also, in case when mc has been launched, closing that tab in ConEmu (i.e. right-click the tab -> Close tab) works fine.

Another note, if I run stermc from standard Windows console, without ConEmu, everything is also fine.

PS: I have a gut feeling that this might somehow be connected with colours, but I cannot really investigate this deeper at the moment. Primarily because of the need to hard-reset very often. I will, however, do anything specific you need me to in order to fix this.

sa1nt commented May 20, 2016

Sorry for late response, but apparently that commit you made didn't really fix the problem.

I cannot recall the precise ConEmu version when this changed, but on ver. 160515 [64] {Preview} the situation is following.

When I type Ctrl+D or exit in the stermc SSH console and I had used Midnight Commander during this session, then CPU usage jumps to 100% and the machine completely stops responding. This, as far as I've found, may be "resolved" only with a hard reset of the PC. I have tried to wait it over, but after 30 minutes nothing's changed, so I still had to hard reset the PC.
ConEmu crash dump doesn't appear after this.

When I type Ctrl+D or exit in the stermc SSH console and Midnight Commander has not been launched during the session, everything's fine.

Also, in case when mc has been launched, closing that tab in ConEmu (i.e. right-click the tab -> Close tab) works fine.

Another note, if I run stermc from standard Windows console, without ConEmu, everything is also fine.

PS: I have a gut feeling that this might somehow be connected with colours, but I cannot really investigate this deeper at the moment. Primarily because of the need to hard-reset very often. I will, however, do anything specific you need me to in order to fix this.

@sa1nt

This comment has been minimized.

Show comment
Hide comment
@sa1nt

sa1nt May 20, 2016

Another interesting thing I've just found.

When performing the "worst case scenario" from a default {Shells::cmd} shell inside ConEmu (i.e. manually executing stermc command with proper parameters), then ConEmu process starts using 25% of CPU (a single core, apparently). The machine remains usable in this case, and it's possible to kill ConEmu process via Process Explorer.

sa1nt commented May 20, 2016

Another interesting thing I've just found.

When performing the "worst case scenario" from a default {Shells::cmd} shell inside ConEmu (i.e. manually executing stermc command with proper parameters), then ConEmu process starts using 25% of CPU (a single core, apparently). The machine remains usable in this case, and it's possible to kill ConEmu process via Process Explorer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment