https://bugs.documentfoundation.org/show_bug.cgi?id=171066
Bug ID: 171066
Summary: Regression in PyUNO / VCL: Headless startup crashes
and File Lock issues in versions 25.4 - 26.2
Product: LibreOffice
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: graphics stack
Assignee: [email protected]
Reporter: [email protected]
Dear LibreOffice Developers / Support Team,
I am writing to report a significant stability issue encountered when
automating LibreOffice via PyUNO on Windows, specifically affecting versions
from 25.4 up to the current 26.2 development builds.
Curiously, the version 25.8.1.1 works perfectly, but the surrounding versions
exhibit severe graphical "glitches" and crashes during the startup and
file-loading phase.
The Setup:
Environment: Python 3.12, Windows 10/11.
Integration: PyUNO via UnoUrlResolver (Socket/Pipe).
Startup Flags: -nologo -minimized -invisible -env:UserInstallation=...
The Issues:
VCL / Skia Regression: In the problematic versions, launching LibreOffice in
-invisible mode frequently leads to immediate crashes. It appears to be related
to Skia/Vulkan initialization. Even when forced to disable Skia via
registrymodifications.xcu, the process remains unstable compared to v25.8.1.1.
loadComponentFromURL & File Locking: When calling loadComponentFromURL with the
AsTemplate=True property, we intermittently receive "Document in use" or "File
Locked" errors (pointing to the current timestamp), even when no other
instances are running. This behavior is inconsistent; version 25.8.1.1 handles
the template creation seamlessly, while 26.2 seems to struggle with the
lock-file management in automated environments.
Questions:
Are there specific changes in the VCL (Visual Class Library) or Skia
integration between 25.4 and 26.2 that could affect headless/invisible startup?
Has the logic for AsTemplate or file-locking changed in recent builds,
specifically regarding how it handles the .~lock file in a custom
UserInstallation path?
Why does 25.8.1.1 maintain stability while newer builds do not? Is there a
specific commit or build flag we should be aware of?
Any insight or suggested workaround (specific -env flags or bootstrap
variables) would be greatly appreciated.
Best regards
--
You are receiving this mail because:
You are the assignee for the bug.
