Description:
A remote user opened .ods file from owncloud using collabora, made changes and reported system slowed to unusable, he closed browser. file was saved correctly but system was almost unusable due to 100% CPU on 1 core taken by process loolforkit 

On server I found loolforkit process (below) taking 100% CPU 2 hours after user saved, process remained open:-

:/proc/2769$ ps -Flww -p 2769
F S UID        PID  PPID  C PRI  NI ADDR SZ WCHAN    RSS PSR STIME TTY          TIME CMD
5 R lool      2769  4971 29  80   0 - 654320 -     1308604 0 janv.30 ?      05:47:15 /usr/bin/loolforkit --losubpath=lo --systemplate=/opt/lool/systemplate --lotemplate=/opt/collaboraoffice6.2 --childroot=/opt/lool/child-roots/ --clientport=9980 --masterport=loolwsd-5Jb6ZzdU --rlimits=limit_virt_mem_mb:0;limit_stack_mem_kb:8000;limit_file_size_mb:0;limit_num_open_files:0 --version

Server setup is:
Collabora online CODE loolwsd 4.2.0 on Ubuntu 18.04 with collabora office 6.2.3
downstream Server configuration ownCloud version: 10.2.1.4
Operating system: Raspbian 9.0 stretch, Web server: Apache/2.4.25 (Raspbian)

Not sure if its a bug or my setup, first time to see. I can't reproduce it, how can I help identify and prevent it?


Steps to Reproduce:
1. unable to reproduce, first time to see this today
2. had to restart loolwsd to clear 
3. still cannot repoduce

Actual Results:
cannot

Expected Results:
I though the problem would reproduce but didn't maybe remote only (outside LAN)


Reproducible: Couldn't Reproduce


User Profile Reset: No



Additional Info:
I believe the loolforkit process should close itself when document is closed, I see 2 new process open and close when I open and close a .ods document but CPU and RAM is very small <5%. 

With no documents open 2 loolforkit process is sleeping at 0%CPU and <5%RAM