|
|
|
Most 749X errors are the result of memory corruption on the host machine. Although these errors are extremely rare, they can be serious. In most cases, restarting FairCom DB will clear a transient memory error. If these errors repeat, please contact your application vendor.
Value |
Cause |
|---|---|
7490 |
A request for memory beyond reasonable limits. |
7491 |
Attempting to return memory carrying an unreasonable large length value in its control header. |
7492 |
Encountered an invalid "availability" counter during a sub-allocator get operation. |
7493 |
An invalid "availability" counter while returning a block of memory. |
7494 |
An invalid header pointer for an allocation block. |
7495 |
A list connected with FairCom DB’s memory sub-allocator has become invalid or corrupted. For single-user, check your parameters passed to our functions. For a server, this is usually a bug. This error has been seen in V11.2.2. due to bad Unicode data. V11.2.3 has been patched to catch bad data and log it instead of passing it into the code, causing a crash. |
7496 |
Failure in memory swapping operation. |
7497 |
Attempting to return memory carrying a zero length in its control header. |
7498 |
An invalid semaphore owner while getting memory. |
7499 |
An invalid semaphore owner while returning memory. |
