https://bugs.documentfoundation.org/show_bug.cgi?id=112877
--- Comment #8 from WilliamGordon <[email protected]> --- This issue arises when a file dialog (FilePicker) is opened before establishing a database connection via ThisDatabaseDocument.CurrentController.connect. Under high memory usage, this sequence prevents the Java Runtime Environment (JRE) from loading correctly, causing the connection and further database editing to fail with a misleading "JRE is corrupt" error. The problem disappears if the database is connected before the dialog opens, indicating a timing or memory contention issue. While reproducibility is difficult due to the macro library’s complexity, the workaround is to ensure the JRE is loaded by connecting to the database early in the macro. https://sortthecourtgames.com -- You are receiving this mail because: You are the assignee for the bug.
