https://bugs.documentfoundation.org/show_bug.cgi?id=147130

            Bug ID: 147130
           Summary: CRASH - Collabora Office SIGABRT - seemingly random
                    crashes on startup
           Product: LibreOffice
           Version: unspecified
          Hardware: ARM
                OS: macOS (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: LibreOffice
          Assignee: [email protected]
          Reporter: [email protected]

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)

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to