https://bugs.documentfoundation.org/show_bug.cgi?id=147508
--- Comment #19 from Alex Thurgood <ipla...@tuta.io> --- (In reply to Thomas Maeder from comment #17) > In System/Library: JavaVirtualMachines > jdk1.8.0_91.jdk > jdk1.8.0_102.jdk > 1.6.0.jdk None of the above versions should really be used with LO anymore on macOS, in fact, some of them are pretty much guaranteed to cause crashes at some stage. I believe that currently accepted versions on macOS are JDK >= 17. For example, I have: /Library/Java/JaveVirtualMachines/jdk-17_aarch64.jdk/Contents/Home as my recognized path to the JDK when using the macOS ARM-build of LO. > So I'd suggest looking in the Spindumps for anything in this direction. I > couldn't find anything, except notice conspicuous waiting calls (mutexwait, > etc.), which agrees with LO becoming unresponsive with essentially zero CPU > usage. So it seems to wait for something that never comes: deadlock / race > condition / bug in JDK? Does that sound realistic? Yes, it could well be an synchronization issue that causes a deadlock - whether that is due to the JDK or not is up for debate, but that kind of deadlock has also happened in the past when instantiating some functional pathway (e.g. formerly automatic spellchecking, or some other Java call). -- You are receiving this mail because: You are the assignee for the bug.
