Description: I just had 5 documents open: one database (filesize ~1.3 MB) two calc documents (filesize ~250 kB each) two writer documents (filesize ~20 kB each) A total of a little more than 1.8 MB in file size. I was surprised to see in the process list that LibreOffice consumed more than 6 GB of memory in this configuration. After closing the database and the two writer documents, the memory consumption was reduced to 5.5 GB. I can't imagine that LO really needs that much, hence I assume some kind of memory leak in one of the modules. Due to that suspicion, I then closed LO completely and started it again with only the two calc documents: total memory consumption is about 750 MB. After opening the database file (without opening a table or anything else), the memory consumption increased to 830 MB. Then I opened a form and searched for a particular entry. The memory consumption increased to 4.9 GB. The consumption gets reduced by 100 MB on closing the form. Closing the database completely, reduces the memory consumption by another 100 MB, i.e. 4.7 GB. After opening the database again and performing the same procedure as before, memory consumption increases to 5 GB. Closing the database again completely then reduces it to 4.9 GB, after a while (5 minutes or so) it lowers itself to 4.8 GB. It seems that there is a lot of garbage hanging around when handling databases... Luckily, many computers nowadays have a two digit number of RAM available, but that's not always the case, and the steady increase upon reopening the database (or another for that matter) can cause a system to stop working. Steps to Reproduce: 1. Follow the procedure described above. I guess that the size of database, number of fields etc. will affect the result. You need to observe the memory consumption during that time. Actual Results: s. above Expected Results: increase of memory consumption by the size of the database file plus a few MB (maybe 100, I have no idea, but certainly less than 1 GB) for the database module, and reducing the memory consumption by (almost) the same amount when closing the database. Reproducible: Always User Profile Reset: No Additional Info: Version: 25.2.2.2 (X86_64) / LibreOffice Community Build ID: 520(Build:2) CPU threads: 12; OS: Linux 6.12; UI render: default; VCL: kf6 (cairo+wayland) Locale: de-DE (de_DE.UTF-8); UI: de-DE 25.2.2-2 Calc: threaded
Tested with Version: 25.2.3.2 (X86_64) / LibreOffice Community Build ID: bbb074479178df812d175f709636b368952c2ce3 CPU threads: 6; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded Opened two Base files, one connected to internal Firebird database, the other connected to MariaDB by direct connection. Many tables in this databases, but no pictures saved in the databases. The whole memory for LibreOffice will be 550 MB after I had opened forms in both Base files, connecting to many tables and views in the databases. Then opened another Base file connected to internal HSQLDB. Only one table with 30000 rows. Memory exceeds to 1,2 GB, when scrolling to last row to 1,7 GB. Closing this field won't set used memory back to 550 MB. Will be 1,7 GB instead. Problem here: Connection is set and will only be cut when whole LO will be closed. Might be this is bug 100850 1. Which database do you use? Internal HSQLDB? 2. Do you save images inside the tables of the database? 3. You are using a version of LO, which is packed by a Linux distribution. Could you please test with the original from de.libreoffice.org?
Sorry, I didn't get a notice about your reply, or I missed it... To your questions: 1. Which database do you use? Internal HSQLDB? yes, HSQLDB 2. Do you save images inside the tables of the database? yes, but only a few (around 30) with low filesize (around 30k each). 3. You are using a version of LO, which is packed by a Linux distribution. Could you please test with the original from de.libreoffice.org? I would love to, but the provided packages do not easily work on my Manjaro (Arch) system. In fact, I don't know how to install a dep or rpm package in Manjaro, and compiling LO from scratch seems to me like a very complicated process because of the many different modules which all depend on each other in different ways.