Today if I open a Text, 2 spreadsheets and 1 presentation they all will be running at "soffice.bin" process. If I need work with a huge spreadsheet ( >10 hundred lines, several columns and many formulas) LibreOffice sometimes "freezes" waiting to finish the operation (Column resize, formula update, etc) and this kind of operations take sometimes up to 30min. I know that huge documents sometimes take too long to process and that's will not be a problem for the user if he still can work with others opened documents, but because all LibreOffice documents are all opened in the "soffice.bin" if one document stops/freeze all others documents that I have opened will freeze too. If we could have every document in a different CPU process we will still can work with others documents even if one document is freezed.
Thanks for reporting.
Seems interesting to see some developers input here. I'm not aware if it is possible, and if so how hard it is to implement. (seems quite hard).
But, as far I can see this is a valid request. Therefore I mark it as an enhancement request and NEW.
This would need to make all code thread safe. Which may not be entirely impossible but would take more than huge effort. More promising probably would be to start thread safety where possible and have parts of the applications run in different threads. Specifically for Calc, work is continuously ongoing into that direction, but it will need much work and take much time.
Summing up, the general "one thread per document" is a nice wish, but IMHO not something we need to have to linger around in the bug tracker.
Just my 0.02
And of course starting two instances with different user profiles will help you already with that.
What do you mean with "different user profiles" ? 2 different users, one for each application ? Of course this works but is not usefull, especially on MS Windows.
I think that, starting each app (Calc, Writer, Impress, etc) in a different CPU process, like MS Office does, can be one initial step.
*** Bug 131686 has been marked as a duplicate of this bug. ***