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

            Bug ID: 173732
           Summary: Writer hangs on open when the document contains a
                    nested group while navigator sidebar is active
           Product: LibreOffice
           Version: 26.8.0.3 release
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
Writer's main thread spins at 100% CPU and the UI never becomes responsive when
opening a document that contains a nested group shape (a group containing
another group), if the Navigator is the last active deck in the Writer sidebar
and Navigator/ActiveBlock is 2811. Headless conversion of the same file works.

I found the settings by bisecting a user profile (1262 registry entries). Both
are needed; removing either one stops the hang:

<item oor:path="/org.openoffice.Office.UI.Sidebar/Content"><prop
oor:name="LastActiveDeck"
oor:op="fuse"><value><it>com.sun.star.text.TextDocument,NavigatorDeck</it></value></prop></item>
<item oor:path="/org.openoffice.Office.Writer/Navigator"><prop
oor:name="ActiveBlock" oor:op="fuse"><value>2811</value></prop></item>

Steps to Reproduce:
1. Create a fresh profile: soffice -env:UserInstallation=file:///tmp/lo-test
--headless --terminate_after_init
2. Add the two <item> entries above to
/tmp/lo-test/user/registrymodifications.xcu, just before </oor:items>.
3. Run soffice -env:UserInstallation=file:///tmp/lo-test test.docx (file is
attached)

Actual Results:
soffice.bin sits at 100% CPU and the window never becomes usable.

Expected Results:
The document opens.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 26.8.0.3 (X86_64)
Build ID: 680(Build:3)
CPU threads: 16; OS: Linux 6.18; UI render: default; VCL: kf6 (cairo+wayland)
Locale: de-AT (en_GB.UTF-8); UI: en-GB
26.8.0-2
Calc: threaded

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

Reply via email to