https://bugs.freedesktop.org/show_bug.cgi?id=60793
--- Comment #2 from jackvd2...@gmail.com --- Hi Michael, I fully agree with you :-) But... Since I was having trouble with another application too (TraderWorkStation) I assumed that there must be a correlation. Eventually I pinned it down to a possible Java problem. Searching for Java performance problems on OSX finally got me to the solution.... As it turned out, a frequently used anti-virus tool on OSX named Sophos was the 'bad' guy. Within Sophos there is an option called 'Scan inside archives and compressed files' in the 'on-access' scanner...... This causes the entire Java runtime environment to be checked on startup! This indeed can take up to 10 minutes before it is done and the runtime gets loaded into memory. Not 'ticking' that option makes the system more vulnerable for infections, but makes the startup delays disappear. For my trading application this made a lot of sense, since it is a Java application. For Writer, this was not that obvious since I was not aware that it actually loads Java code during the opening of a document. What saved me was the marketing machine of Oracle :-) While experimenting with Java, I replaced the Apple runtime with the native Oracle one. And every time the Java runtime gets started, a popup window appears telling me how good Oracle Java really is :-). This is how I discovered that Writer indeed calls the Java environment after loading a document. Hopefully this will help other people too, because I did see more issues around loading delays on OSX. Thx for your time! Ciao; Jack -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs