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

--- Comment #4 from [email protected] ---
Bug Report / Case Synopsis
Environment:

OS: Windows 11 Home (64-bit, Version 25H2, Build 26200.8457)

Hardware: Intel Core i3-8100 CPU @ 3.60GHz, 8.00 GB RAM

Storage: Local Dual-Drive System (SSD + HDD configuration)

Original LibreOffice Behavior: Working within a large Master Document (.odm)
managing approximately 37 sub-documents (.odt), totaling over 110,000 words.

Description of Event & Symptoms
Abrupt Un-linking of Sub-Documents: During an active local writing and editing
session, approximately 10 individual sub-documents suddenly vanished entirely
from the Navigator hierarchy panel. The files were verified to be completely
intact on the local file system, but the Master Document completely dropped
their references from its active index.

UI Rendering and Focus Failures: Subsequent attempts to reload the Master
Document (.odm) resulted in severe interface lockups. The Navigator panel
interface lost its "Master Document View" capabilities. Crucial structural
tools—including the Insert (File) icon and chronological arrangement
arrows—disappeared or became completely greyed out, even though the window
title bar explicitly identified the file extension as .odm.

Sub-document Focus Trap: When forced to open via recovery, the UI erroneously
trapped the main viewing window in a read-only view of a single blank
sub-document section, misreporting the global document statistics as 0 words, 0
characters on Page 1 of 1, despite the underlying .odm file structure still
retaining a size profile consistent with its cached data.

Technical Artifacts & Suspected Root Cause
Registry Corruption: Investigation into the user profile directories revealed
that the master configuration file registrymodifications.xcu was forced to do a
background write operation immediately preceding the crash.

File Inspection: Upon opening the updated registrymodifications.xcu file in a
text editor, severe formatting anomalies and non-textual "hash/garbage data"
were present in the middle of the XML document layout, indicating an
interrupted or corrupted plain-text write operation.

Race Condition / Cloud Lock: The directory containing the .xcu file exhibited
an active green checkmark overlay from a background file synchronization/backup
utility. It is highly suspected that a microsecond race condition occurred:
LibreOffice attempted a massive plain-text configuration write while the system
sync utility simultaneously locked the file for indexing, causing a
catastrophic memory flush that truncated the Master Document's UI pointers.

Current Status
The user has bypassed the corrupted document environment by performing a clean
upgrade to LibreOffice 26.2.3 (Windows x86-64) and recreating the master
framework from scratch to maintain workflow continuity.

Because the original environment has been altered, the corrupted configuration
file has been isolated, and the workflow has shifted to the updated version, no
further debugging steps, log captures, or reproduction trials can be provided
by the reporter for this specific ticket instance. The QA team may close this
ticket or use these notes to investigate background file-locking
vulnerabilities during intense .xcu write actions.

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

Reply via email to