I’ve recently added some automated alerts to my systems, so that whenever a [hdls] entry goes into the diagnostic log: I get an automated alert.
The vast majority of alerts that I’m getting come from my own ON ERR CALL method: I’m doing this:
ARRAY LONGINT($aErr_Codes;0) ARRAY TEXT($aErr_CompCodes;0) ARRAY TEXT($aErr_Text;0) GET LAST ERROR STACK($aErr_Codes;$aErr_CompCodes;$aErr_Text) $Cnt_i:=Size of array($aErr_Codes)
The [hdls] error is being logged on the last line: where I’m check the size of array:
Error: #52 An array was expected or the type of the array was not appropriate.
It seems to me that at this point: 4D is having some kind of a memory management error: where it can’t allocate ram to create an array.
I’m looking for good advice for
- 1: Why does this happen?
- 2: is there any way to prevent this?
- 3: Once I’m in this situation :is there any way to help 4D to recover within the current process?
4D keeps running (does not crash, fortunately), but the process seems to be stuck.