https://bugs.documentfoundation.org/show_bug.cgi?id=135073
Stéphane Guillou (stragu) <stephane.guil...@libreoffice.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |stephane.guillou@libreoffic
| |e.org
OS|All |Windows (All)
See Also| |https://bugs.documentfounda
| |tion.org/show_bug.cgi?id=13
| |5072
--- Comment #14 from Stéphane Guillou (stragu)
<stephane.guil...@libreoffice.org> ---
With comment 12 steps:
No repro on Linux:
BigPtrArray crash at step 6, but at step 9, but LO closes, and Ubuntu Apport
catches the crash. Reopening LO goes directly to reporting the step 6 crash,
and then the document recovery works.
Version: 7.6.6.3 (X86_64) / LibreOffice Community
Build ID: d97b2716a9a4a2ce1391dee1765565ea469b0ae7
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: CL threaded
On Windows 11, I get the crash at step 6, and then "Document are being saved"
is stuck on step 9 with progress bar not moving. If I close that dialog and
restart LO, I get the crash report dialog, with signature
"BigPtrArray::Index2Block(long)":
-
https://crashreport.libreoffice.org/stats/crash_details/fa9252b3-d5df-4605-9d10-6edc7f42a120
-
https://crashreport.libreoffice.org/stats/crash_details/99030566-c721-4ae7-b885-26253eab36a4
... but that's the step 6 (bug 135072) crash that's reported after, correct?
After the crash report dialog, the document recovery works as expected.
Version: 7.6.6.3 (X86_64) / LibreOffice Community
Build ID: d97b2716a9a4a2ce1391dee1765565ea469b0ae7
CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
So, is the issue that the "Documents are being saved" freezes?
--
You are receiving this mail because:
You are the assignee for the bug.
