Faulting – hcitcl.exe – nightly scripts

[Eric Wright]

Hello all,

I’m running Cloverleaf version 20.1.1.1P on a Windows 2016 Server Standard.

When running the nightly scripts to cycle_save all of the log files and move them to an archive area, I’m getting the following error that I’ve never seen.  I’m getting it at different parts of the script on some nights, and not getting it at all on other nights.  For instance, it appears that it threw this error a few nights ago when it went to run hciprocstatus, and a few nights before that it threw an error somewhere else.  Does anyone happen to know what would cause this issue:

Faulting application name: hcitcl.exe, version: 0.0.0.0, time stamp: 0x60dde420
Faulting module name: ntdll.dll, version: 10.0.14393.7426, time stamp: 0x66f60107
Exception code: 0xc0000374
Fault offset: 0x00000000000f7103
Faulting process id: 0x918
Faulting application start time: 0x01db5f266d16a3d8
Faulting application path: c:\cloverleaf\cis20.1\integrator\bin\hcitcl.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: c16680a7-6bab-4c9b-8a8c-c907922f72c7
Faulting package full name:
Faulting package-relative application ID:

 

I ran the hciprocstatus command a few times in a row through the command prompt to test to see if there was any issues, but it ran without a problem.

Thanks for the help in advance,

Eric W.

Topic

[David Barr]

Exception code 0xc0000374 is “heap corruption”. The codes are documented here. I’m not sure what could cause this.

[Charlie Bursell]

Usually cause by memory overwrites.  Try put all the command in catch statements.  A shot in the dark would be to unset variables once used.

 

Good luck with it.  Problems like this can be a bitch troubleshoot

[Jason Russell]

Another question (We’ve seen this in other areas), if you’re pulling the log file data itself into memory, how BIG are your files? If you’re simply moving the files without pulling them into memory it shouldn’t cause a problem, but if you’re reading the file into memory, if they’re large (I know they can get big, quickly if you have echo’s or various levels of verbose turned on).

Could you share your script? May be something in the script itself that someone could point out that may be causing issues.

Just thinking in high-level thoughts, the other possible problem is potentially the script is running too quickly, especially if the files are exceptionally large. If you’re moving a file, and then trying to access the file at the same time (log is writing to the log file) that could potentially cause issues as well.

[Author]

Replies