Bug#910905: libreoffice: soffice.bin --headless launched from unoconv/odt2txt memory bomb / not terminating

[Rene Engelhard <rene@debian.org>]

tag 910905 + moreinfo
thanks

On Sat, Oct 13, 2018 at 10:27:44AM +0200, Marcel Partap wrote:
> My ranger curses file manager invokes `odt2txt --stdout` (which would be a good

Out of odt2txt or out of unoconv?

$ apt-file search odt2txt
firejail-profiles: /etc/firejail/odt2txt.profile
odt2txt: /usr/bin/odt2txt.odt2txt
odt2txt: /usr/lib/mime/packages/odt2txt
odt2txt: /usr/share/doc/odt2txt/README.Debian
odt2txt: /usr/share/doc/odt2txt/changelog.Debian.amd64.gz
odt2txt: /usr/share/doc/odt2txt/changelog.Debian.gz
odt2txt: /usr/share/doc/odt2txt/copyright
odt2txt: /usr/share/man/man1/odt2txt.odt2txt.1.gz
unoconv: /usr/bin/odt2txt.unoconv
unoconv: /usr/share/man/man1/odt2txt.unoconv.1.gz

Your subject suggests the latter, but...

> default for odt2txt by the way) for document previews. The `soffice.bin
> --headless` (haha still *office binary lol) seems to be a server process that

Backwards-compatibility. Yeah, don't like it either :-)

> does not automatically exit.

I think it does when you do --convert-to. Otherwise I think the program
using LO needs to take care of this...

>  Occasionally it has hit some thing where it would consume all my memory
> (24GB+24GB swap).
> Is there some way to limit the maximum memory this process shall eat via some
> systemd / cgroups / ulimit conf?

Yes, most probably? Not a bug here, though?

> Timing out the server would also be a good idea in my opinion. Wouldn't it?

There's no "server" here. You are running a "normal" LibreOffice. (in
headless mode).

--listen= etc. would be "server" mode if you wish. But I think unoconv
does this?

Regards,

Rene