vdbs destroyed because of out-of-memory

[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.


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]