4D v14.3OS Memory Manager Errors (-117 -> -108) |
||||||||||||||||||||
|
4D v14.3
OS Memory Manager Errors (-117 -> -108)
|
Code | Description |
-117 | Internal Memory problem. Memory is probably logically corrupted. |
Exit as soon as possible. Restart your machine and reopen the database. | |
-111 | Internal Memory problem. Memory is probably logically corrupted. |
Exit as soon as possible. Restart your machine and reopen the database. (*) | |
-109 | Internal Memory problem. Memory is probably logically corrupted. |
Exit as soon as possible. Restart your machine and reopen the database. | |
-108 | Not enough memory to perform an operation. |
Give more memory to your 4D application. |
Tip: When allocating and working with large arrays, BLOBs, pictures, as well as sets (objects that can hold large amount of data), use an ON ERR CALL. project method to test the error -108.
(*) Error -111 can also occur when you attempt to read a value from a BLOB with an offset out of range. In this case, the error is minor and you do not need to terminate the working session. Just fix the offset you pass to the BLOB command.
Product: 4D
Theme: Error Codes
4D Language Reference ( 4D v12.4)
4D Language Reference ( 4D v11 SQL Release 6)
4D Language Reference ( 4D v14 R3)
4D Language Reference ( 4D v14 R2)
4D Language Reference ( 4D v13.5)
4D Language Reference ( 4D v14.3)
4D Language Reference ( 4D v14 R4)