Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
0.4.9-dev-60-g1dfbed9 https://github.com/reactos/reactos/commit/1dfbed9c3dbd135c7bf51090b9cadde6d2642340
Description
reactos-bootcd-0.4.14-dev-1455-g963d39b-x86-gcc-lin-dbg
Click on "close" on the service start/stop Progress Windows does nothing and leads to error with 0x0 winwow handle and Pipe write failure
This is due to "Close" being IDOK (leading to window closure request) while the "infinite loop" waiting for Service to reply being still running in DoControlService / DoStopService / DoStartService functions in a dedicated thread which is not stopped.
IDD_DLG_PROGRESS DIALOGEX 6, 6, 255, 89 |
CAPTION "Service Control" |
FONT 8, "MS Shell Dlg", 0, 0 |
STYLE DS_SHELLFONT | WS_BORDER | WS_DLGFRAME | WS_SYSMENU | WS_VISIBLE | DS_MODALFRAME
|
BEGIN
|
CONTROL "", IDC_SERVCON_PROGRESS, "msctls_progress32", 0x50000000, 8, 46, 238, 13 |
LTEXT "", IDC_SERVCON_INFO, 8, 5, 236, 11 |
LTEXT "", IDC_SERVCON_NAME, 8, 25, 66, 11 |
PUSHBUTTON "&Close", IDOK, 100, 70, 54, 13 |
END
|
Attachments
Issue Links
- blocks
-
CORE-17314 WlanSvc can not be stopped
- Open
-
CORE-15279 Can't stop RosAudioSrv
- Reopened
-
CORE-16949 Stopping Printer Spooler service takes more than 1 minute (+NULL windows handle if closed)
- Reopened
- relates to
-
CORE-14390 DHCPSVC is not allowed to be stopped
- Reopened
-
CORE-14340 UltraVNC 1.2.1.7 service fails to stop
- Untriaged
-
CORE-15314 [servman] does not recognize a crashed service to be not running / stopped
- Untriaged