vdbs destroyed because of out-of-memory

[Thomas Flemming]

Hi Ruslan,

 > This should not happens in 5.0 and better thanks to journal on db.

can you please explain more detailed, why 5 is more reliable then 4.9?
What exactly makes the difference with journal on db?

We are planning the new major release of our software and to be honest, we are 
considering to move to MySql or MariaDb, just because of too much trouble with 
destroyed vdbs.
Stability is just the most important thing!

Tom


Am 18.12.2013 11:50, schrieb Ruslan Zasukhin:
> On 12/17/13, 5:47 PM, "Thomas Flemming" <tf at qvgps.com> wrote:
>
>> Hi,
>>
>> how is this possible?
>>
>> my software is using VNET-client 4.9 with local databases, no vserver and also
>> using some libs for image-processing.
>>
>> A customer was trying to open a very large bitmap-image, which was resulting
>> in an out-of-memory error and a crash of the program.
>>
>> This crash destroyed all vdb-databases which were currently open for
>> read-write. Read-only databases were not destroyed.
>> Destroyed means, that they all have a length of 1GB now on disc and that they
>> can't be open or compress any more.
>>
>> How is this possible? How can an out-of-memory in a image-lib affect vnet in
>> such way?
>
> Hi Thomas,
>
> This should not happens in 5.0 and better thanks to journal on db.
>
>

-- 
/****************************************
**   Flemming Software Development CC
**   Thomas Flemming
**   PO Box 81244
**   Windhoek, Namibia
**   http://www.quovadis-gps.com
**   mail  tf at qvgps.com
**   +264 (0)81 3329923
**   +49  (0)6182 8492599
***************************************/