Home » Search

About memory

91-100 of 159Refresh
Forum
1

ObjectDB shuts down

starts to kill processes if it runs out of memory, in order to keep the necessary amount of RAM ... too much memory (out of the total available), thus CentOS was killing it. We monitored the DB server RAM
Forum
1

ObjectDB version 2.3 has been released

[] by reducing required storage space. Removed a shutdown hook that leads to memory leak (issue #453). Completed missing documentation (e.g. UPDATE & DELETE queries). Fixed memory leak issues. Fixed
Forum
1

Optimistic lock

the retry code after the exception can I assume the changes I made to the object in memory are retained ... after transaction failure (regardless of cause) retain their values in memory. Objects can be restored
Forum
1

OutofMemory error with Object DB 2.0

(currently 500) records                 // This is becasue ObjectDB keeps all items in memory ... database there is a cache memory problem. The heap dump may help in understanding the problem. Does it mean
Forum
1

Performance with large databases

be held fully in memory or some such issue?  The method calls that suddenly start ... , the entire database can reside in memory (using the OS cache, regardless of the JVM heap size
Issue
1

Server crash - Mismatch client-server protocol prefix

out-of-memory errors (although I'm running with -Xmx1024m) and some issues with a particular index ... message after eliminating the memory and index issues? Update: Apparently this exception
Forum
1

Tutorial issue

previously and the database had a memory of it. By starting with a new database that memory was erased
Issue
1

Unexpected error when loading all entity instance

find a way to reproduce the error now. It seems there was insufficient memory on the maschine. I will observe the issue and update if I find a way to reproduce it. Best wishes Insufficient memory
Result
1

ObjectDB version 2.0.0

finding an entity after a failed find followed by persist. Fixed a memory leakage in eager load
Result
1

ObjectDB version 2.4.4

Version 2.4.4 Improved memory management when handling very large transactions (issue #935). Improved the Doctor to handle additional situations. Added support in retrieving metamodel without connection (feature request #896). Added support of disabling logging. Improved missing license