https://bugs.documentfoundation.org/show_bug.cgi?id=92529
--- Comment #6 from Stephan Bergmann <[email protected]> --- (In reply to Chris Halls from comment #5) (1) While writing the configuration changes happens asynchronously in its own thread, it does lock a configuration-wide mutex, so other threads trying to access the configuration can get blocked. (2) What may already help the performance of some use cases (though probably not the above NFS case) is <http://cgit.freedesktop.org/libreoffice/core/commit/?id=e1d78e123b74d37f95b4075b93202b023b4320e9> "tdf#92764 - make configmgr write less noisy." (3) Re "An ugly workaround may be to disable configuration changes completely by setting profile folder read-only" (<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774399#5>): Since <http://cgit.freedesktop.org/libreoffice/core/commit/?id=12f92e6d9ea8bf05bda6d3c42f9b6f0aba000cb0> "Support modification write-back to other than registrymodifications.xcu," you can change the "user:" entry in LO's fundamentalrc CONFIGURATION_LAYERS line from "user:..." (or "user:!...") to "user:*..." to not write any new updates to registrymodifications.xcu (but still read in an already existing one on startup). (And on older versions, just removing the "user:" entry from CONFIGURATION_LAYERS should work to not read nor write registrymodifications.xcu). For better or worse. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
