Cygwin 'cp' command is still slow after Cygserver is installed
Derek Pagel
Derek.Pagel@infor.com
Tue Apr 11 20:07:53 GMT 2023
I've been seeing an issue where Cygwin commands sometimes take a while to complete, or they will not complete at all and will have to be manually killed through task manager. I installed Cygserver and that helped to lessen the number of times that the issue happens but it didn't get rid of it. I'm wondering if anyone has run into the same behavior. I've also shared the .dmp files of a 'cp' command that was taking a while to complete in case that helps:
cp.dmp
Microsoft (R) Windows Debugger Version 10.0.22621.755 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\sandbox\Logs\cp.dmp]
User Mini Dump File with Full Memory: Only application data is available
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 17763 MP (8 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Edition build lab: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Debug session time: Tue Apr 4 11:13:23.000 2023 (UTC - 5:00)
System Uptime: 38 days 11:52:56.830
Process Uptime: 0 days 0:21:50.000
.......
For analysis of this file, run !analyze -v
ntdll!NtWaitForSingleObject+0x14:
00007ffd`f967f7e4 c3 ret
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 327
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 1001
Key : Analysis.Init.CPU.mSec
Value: 624
Key : Analysis.Init.Elapsed.mSec
Value: 13453
Key : Analysis.Memory.CommitPeak.Mb
Value: 80
Key : Timeline.OS.Boot.DeltaSec
Value: 3325976
Key : Timeline.Process.Start.DeltaSec
Value: 1310
Key : WER.OS.Branch
Value: rs5_release
Key : WER.OS.Timestamp
Value: 2018-09-14T14:34:00Z
Key : WER.OS.Version
Value: 10.0.17763.1
FILE_IN_CAB: cp.dmp
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0
FAULTING_THREAD: 000019f0
PROCESS_NAME: cp.exe
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE_STR: 80000003
STACK_TEXT:
00000000`004fe608 00007ffd`f61783d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`004fe720 : ntdll!NtWaitForSingleObject+0x14
00000000`004fe610 00000000`677ea815 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`000000c8 : KERNELBASE!WaitForSingleObjectEx+0x93
00000000`004fe6b0 00000000`677eb688 : 00000000`00000000 00000000`00ae6bd0 00000000`00000000 00000000`00000000 : msvcr90!_dospawn+0x261
00000000`004fe7d0 00000000`677eb831 : ffffffff`ffffffff 00000000`00ae4cb0 00000000`00000000 00007931`45513238 : msvcr90!comexecmd+0x78
00000000`004fe820 00000000`677ebd0a : 00000000`00000000 00000000`00ae4c20 00000000`00000000 00000000`00000000 : msvcr90!_spawnve+0x17d
00000000`004fe890 00007ff7`afc11261 : 00000000`00ae6bd0 00000000`00000003 00000000`004fed20 00000000`004fe920 : msvcr90!system+0xaa
00000000`004fe8f0 00007ff7`afc11442 : 00000000`00000000 00001e3c`d7e4c5c9 00000000`00000000 00000000`00000000 : cp+0x1261
00000000`004ffd40 00007ffd`f9227974 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cp+0x1442
00000000`004ffd70 00007ffd`f964a271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000000`004ffda0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
STACK_COMMAND: ~0s; .ecxr ; kb
FAULTING_SOURCE_LINE: f:\dd\vctools\crt_bld\self_64_amd64\crt\src\dospawn.c
FAULTING_SOURCE_FILE: f:\dd\vctools\crt_bld\self_64_amd64\crt\src\dospawn.c
FAULTING_SOURCE_LINE_NUMBER: 215
SYMBOL_NAME: msvcr90!_dospawn+261
MODULE_NAME: msvcr90
IMAGE_NAME: msvcr90.dll
FAILURE_BUCKET_ID: BREAKPOINT_80000003_msvcr90.dll!_dospawn
OS_VERSION: 10.0.17763.1
BUILDLAB_STR: rs5_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 9.0.30729.9518
FAILURE_ID_HASH: {ae098e47-a4ce-0039-c30c-1cea11724b06}
Followup: MachineOwner
---------
cp2.dmp:
Microsoft (R) Windows Debugger Version 10.0.22621.755 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\sandbox\116929941_cp\cp2.dmp]
User Mini Dump File with Full Memory: Only application data is available
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 17763 MP (8 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Edition build lab: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Debug session time: Tue Apr 4 11:13:35.000 2023 (UTC - 5:00)
System Uptime: 38 days 11:53:08.253
Process Uptime: 0 days 0:22:02.000
....................
For analysis of this file, run !analyze -v
*** WARNING: Unable to verify timestamp for cygwin1.dll
ntdll!NtQueryObject+0x14:
00007ffd`f967f964 c3 ret
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 421
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 943
Key : Analysis.Init.CPU.mSec
Value: 264
Key : Analysis.Init.Elapsed.mSec
Value: 127055
Key : Analysis.Memory.CommitPeak.Mb
Value: 70
Key : Timeline.OS.Boot.DeltaSec
Value: 3325988
Key : Timeline.Process.Start.DeltaSec
Value: 1322
Key : WER.OS.Branch
Value: rs5_release
Key : WER.OS.Timestamp
Value: 2018-09-14T14:34:00Z
Key : WER.OS.Version
Value: 10.0.17763.1
FILE_IN_CAB: cp2.dmp
NTGLOBALFLAG: 0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
APPLICATION_VERIFIER_FLAGS: 0
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0
FAULTING_THREAD: 00005dd4
PROCESS_NAME: cp.exe
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE_STR: 80000003
STACK_TEXT:
00000000`fffdc9b8 00000001`80059050 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!NtQueryObject+0x14
00000000`fffdc9c0 00000001`8005b483 : 00020000`00000011 00000008`00000010 00000001`8034d860 00000001`8034de70 : cygwin1!dlfork+0xa0
00000000`ffffca50 00000001`8005ba3d : 00000000`00000001 00000001`800d87de 00000000`00000000 00000000`00000000 : cygwin1!dlfork+0x24d3
00000000`ffffcb50 00000001`80048c3f : 00000000`ffffcc10 00000024`00048a70 00000000`00000000 ffffffff`ffffff85 : cygwin1!dlfork+0x2a8d
00000000`ffffcbd0 00000001`80047746 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cygwin1!cygwin_dll_init+0x38f
00000000`ffffcd80 00000001`800477f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cygwin1!_assert+0x41f6
00000000`ffffcdd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cygwin1!_assert+0x42a4
STACK_COMMAND: ~0s; .ecxr ; kb
SYMBOL_NAME: cygwin1+a0
MODULE_NAME: cygwin1
IMAGE_NAME: cygwin1.dll
FAILURE_BUCKET_ID: BREAKPOINT_80000003_cygwin1.dll!Unknown
OS_VERSION: 10.0.17763.1
BUILDLAB_STR: rs5_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 3003.3.0.0
FAILURE_ID_HASH: {6e59254d-04c5-5897-9d5c-9c053de3947f}
Followup: MachineOwner
---------
More information about the Cygwin
mailing list