|
|
|
|
|
|
|
|
|
|
version 6.0
The following table lists the error codes returned by the Operating System Memory Manager.
| Code | Description |
| -108 | Not enough memory to perform an operation. |
| Give more memory to your 4D application. | |
| -109 | 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. (*) | |
| -117 | Internal Memory problem. Memory is probably logically corrupted. |
| Exit as soon as possible. Restart your machine and reopen the database. |
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.
See Also
|
|
|
|
|
|
|
|
|
|