Quote:
Originally Posted by Prodigy
@Henkie2
Only a newbie attempt, far from skilled 
@UltraFine
I see, but does it run fine so far without crashes on windows 7? |
Hello Prodigy,
I ran the test here, the result: It crashed both SCHEDULER calls again. Here are the details:
[SCHEDULER]
1. Newday at 0 o'clock 10 Minutes
ioA.exe NEWDATE
2. searchlog at 4 o'clock 0 Minutes
ioA.exe SEARCHLOGCREATE
The first script made ioftpd crash so hard that no dump files were created and ioftpd was DELETED. It was not in the directory anymore. The second time , after I have copied it back from the RAR file into the /sysdirectory and restartet it, it crashed again on searchlog at 4am in the morning.
TINYDUMP-20181221.040022-27124.dmp - 56kb
MINIDUMP-20181221.040022-27124.dmp - 643kb
ioFTPD File - size: 475 KB (486.912 Bytes), date: 18.12.2018 21:05:24
/lib directory is a unchanded copy out of the RAR archive belonging to the abobe ioftpd.exe
Test machine: Windows 10
CRASH-Log.txt
Fri Dec 21 04:00:22 2018 - ioFTPD v7.7.3
Unhandled exception: Access Violation (0xC0000005)
Address: 0x004114A9 [attempting to read data from 0x00000006]
PID=27124, PATH=C:\ioFTPD\system\ioFTPD.exe
Thread ID: 29580
System information:
Processor #0 Name: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz
Processor #0 Identifier: Intel64 Family 6 Model 23 Stepping 10
Processor #1 Name: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz
Processor #1 Identifier: Intel64 Family 6 Model 23 Stepping 10
OS: Windows 6.2 (build 9200)
Registry: Windows 10 Enterprise
Decoded: Vista
Page size: 4096
Notice: Unable to acquire Debug Rights
The SEARCHLOGCREATE ioA script is configured to scan a huge harddrive with alot of directories and file which it puts into a plain text file
search.log. The script DID run and it managed to create the search.log file which became 56MB in size. It seems the script crashed ioftpd AFTER it finished its work.
I will send you the dump files per E-Mail.
UltraFine
P.S. I tried the same test on my Win7-64 machine and it worked without a crash. The only difference was that I had a very little directory tree to scan for search.log on win7 machine. Maybe like 50 directories and sub-dirs. It produced a searchlog of 20kb. The searchlog on Win10 machine was way bigger and produced 56MB.