Re: Quitting Omnis due to unrecoverable error: Insufficient memory available: XEXTCODE.cpp:401
I assume you are using the V3 dam’s to talk to oracle …..
if so, I recall at one point in time that we had crashing of omnis talking to postgres – circa Studio 4.3. It took a lot of tracing and as I recall, what we eventually uncovered was a bug in the dam’s where it was converting some numeric info from the database to omnis vars in the list. It was small/subtle and took time to cause it to crash as omnis slowly took up a little more memory .. until it hit a problem.
so, if the crash is generally dependant on the amount of work that the application is doing, that might be the issue .. which would be an issue in the core …. not something that can easily be addressed.
see you at the third annual users conference
> On Nov 9, 2017, at 9:25 AM, Chris Webb <Chris.Webb@catalina-software.co.uk> wrote:
> Hi All,
> Every so often and only on certain PCs during data processing the error “Quitting Omnis due to unrecoverable error: Insufficient memory available: XEXTCODE.cpp:401” is displayed and Omnis closes.
> I have looked through the forums for this error and can only find similar posts but with different error codes. This occurs sporadically during processing and involves inserts/updates to an Oracle DB but all commits happen in line with processing and there is no bulk insert/update/commit occurring.
> This is mainly observed on a 64bit windows 10 machine running Omnis v4.3.
> Event logs for the crash show an issue relating to omnis.exe and msvcrt.dll
> Any thoughts / suggestions would be greatly appreciate.
> Thanks in advance
> Chris Webb
> Senior Omnis Developer
> Catalina Software Ltd.
> Manage your list subscriptions at lists.omnis-dev.com
Manage your list subscriptions at lists.omnis-dev.com