Hi,
we have two different services for windows 10/2019 x64. They are build with the lazdaemon package.
It is working as expected for few hours up to several days. Then the service crashes with following event view entry:
Faulting application name: aservice.exe, version: 4.4.0.7, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.14393.3986, time stamp: 0x5f77fd0d
Exception code: 0xc0000374
Fault offset: 0x00000000000f6fb3
Faulting process id: 0x10a4
Faulting application start time: 0x01d6d7a4fd4d31ea
Faulting application path: C:\aservice\bin\aservice.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: a5684795-7a9d-4cc4-b4ac-39136047d481
Faulting package full name:
Faulting package-relative application ID:
We have created our service like the cleandirs example.
TAService = class(TDaemon)
procedure DataModuleCreate(Sender: TObject);
procedure DataModuleDestroy(Sender: TObject);
procedure DataModuleShutDown(Sender: TCustomDaemon);
procedure DataModuleStart(Sender: TCustomDaemon; var OK: boolean);
procedure DataModuleStop(Sender: TCustomDaemon; var OK: boolean);
private
_working_thread: TWorkingThead;
end;
We tried to cover every line of code for exception handling. And we also using the Application.OnException event to log the error without success.
Has anyone made some experience with uncaught expections in services? We have already tried to change the release settings to debug without a result.
Best regards,
antispam88
Lazarus: 3.0.8
FPC: 3.0.4
X86x_64-wind64-win32/win64
Windows 10 prof. 64x