https://bugs.documentfoundation.org/show_bug.cgi?id=146845
--- Comment #6 from Albrecht Müller <[email protected]> --- (In reply to Telesto from comment #5) > The loop sounds like the process soffice.bin not being terminated after the > crash. It likely a process maxing out a single core.. should be visible in > the process manager As I don't know a way reproduce the bug reliably I cannot check this problem but I think I one time saw a lot of soffice.bin processes, most of them in grey. Don't know what this meant – probably they were finished and ready for removal. I suspect that Writer has some memory leak that eats up slowly (hours, you need to work on documents of some minimum size to notice it) physical memory and therefore removing the processes may take time as it requires to free gigabytes of swap files. Probably the soffice.bin process fails at some point and starts a new instance to fix that failure which fails again etc. Just guessing. My first guess was that the problem is related to Base as this component sometimes produces backup files at a similar rate (several files per second until you do something to stop it, I noticed this by the sound of the hard disk) but now I think the two features are two independent problems. > LibreOffice 7.0.4.2 is also rather old. So maybe check 7.2.x.x first? According to my experience substantial improvements in areas I consider important are pretty rare. Therefore I installed some extensions, developed various workarounds and implemented a few UNO based tools myself. Sometimes I encountered bad regressions so I fear my workarounds and tools may cease to work when I switch to a new version. That's why I am somewhat reluctant to update to new versions. -- You are receiving this mail because: You are the assignee for the bug.
