vdbs destroyed because of out-of-memory

[Thomas Flemming]

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?

Tom

-- 
/****************************************
**   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
***************************************/