Description: Seemingly random crashes on startup or shortly thereafter with Collabora Office 21.06.9001 : Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000010 Exception Codes: 0x0000000000000001, 0x0000000000000010 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [3179] VM Region Info: 0x10 is not in any region. Bytes before following region: 4340875248 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 102bc8000-102bcc000 [ 16K] r-x/r-x SM=COW ...MacOS/soffice Kernel Triage: VM - pmap_enter failed with resource shortage VM - pmap_enter failed with resource shortage VM - pmap_enter failed with resource shortage VM - pmap_enter failed with resource shortage VM - pmap_enter failed with resource shortage Steps to Reproduce: Start Collabora Office by double-clicking in the Applications folder Actual Results: Crash and restart Expected Results: No crash Reproducible: Always User Profile Reset: Yes Additional Info: Process: soffice [3179] Path: /Applications/Collabora Office.app/Contents/MacOS/soffice Identifier: com.collabora.libreoffice Version: 21.06.9001 (21.06.9001) Code Type: ARM-64 (Native)
Created attachment 177992 [details] MacOS system diagnostic report Enclosing system diagnostics report generated by crash.
Something similar was reported here : https://ask.libreoffice.org/t/libreoffice-6-2-crashes-crashes-on-mac-os-catalina-after-a-while/45859
Although I'm not surprised by the "purge" currently being carried out given the tensions between some members of the Board, once can't really tell people to report bugs about Collabora Productivity for several years to the LibreOffice BZ instance, and then simply cancel the reports as NOTOURBUG, absent some policy decision taken by the Board/ESC to no longer accept them. Additionally, there is currently no mechanism for reporting bugs about Collabora Productivity to Collabora - the github issues page is for CollaboraOnline, and the LibreOffice for Android still points to LO BZ for report bugs. A consistent approach is required.
Nobody is purging anyone. Please stop the PARANOIA. If Collabora hosts its own Jenkins to avoid overloading the TDF's resources, why shouldn't they host their own bug tracking system? Don't we redirect Snap bugs to Launchpad.net? Do CIB abuse the TDF's resources? No, right? And why would TDF volunteers waste their time triaging any downstream project's bugs?
As I don't use Collabora Office any more, and it has remain unconfirmed here because of the diverging release paths between Collabora and the LO project, there is not much point in keeping this one open, which was specific to Collabora Office.