Bug 142019 - Crash after reopen a special saved file
Summary: Crash after reopen a special saved file
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.2.0.0.alpha0+
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-01 13:55 UTC by Regina Henschel
Modified: 2021-12-26 04:22 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: https://crashreport.libreoffice.org/stats/crash_details/4e090709-6128-4790-bd6c-dc656e6e9269


Attachments
file to reproduce the crash (62.48 KB, application/vnd.oasis.opendocument.spreadsheet)
2021-05-01 13:55 UTC, Regina Henschel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Regina Henschel 2021-05-01 13:55:46 UTC
Created attachment 171567 [details]
file to reproduce the crash

Open attached file in LO 7.2
'Save as' with new name.
Reload saved file. => Crash.

I see the error with Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: f81871ccbbe118b4ac93325a29f7c6b26765cb6e
CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win
Locale: de-DE (en_US); UI: en-US
Calc: CL
Comment 1 Harshita Nag 2021-05-01 15:51:22 UTC
Can't reproduce it in my system.

ADDITIONAL INFO:

Version: 7.2.0.0.alpha0+ / LibreOffice Community
Build ID: 27911b0455d8dcc08a0702372492a6ce00250cb7
CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: gtk3
Locale: en-IN (en_IN); UI: en-US
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-04-12_15:34:11
Calc: threaded
Comment 2 Vadym 2021-05-24 08:54:47 UTC
Thank you for reporting the bug. I can not reproduce the bug

Version: 7.2.0.0.alpha1+ (x64) / LibreOffice Community
Build ID: b1c0734ffe0f395757b6e0cea7830d820231afeb
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Comment 3 laurent combe 2021-05-24 09:32:50 UTC
can't reproduce

with 

Version: 7.1.3.2 / LibreOffice Community
Build ID: 10(Build:2)
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3
Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR
Ubuntu package version: 1:7.1.3~rc2-0ubuntu0.18.04.1~lo1
Calc: threaded
Comment 4 Buovjaga 2021-05-28 06:05:39 UTC
No crash.

Does it also happen in safe mode?

Version: 7.2.0.0.alpha1+ (x64) / LibreOffice Community
Build ID: 187136265d26c014e842550c2f1fc5997736e4fa
CPU threads: 2; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: fi-FI (fi_FI); UI: en-US
Calc: threaded Jumbo

Arch Linux 64-bit
Version: 7.2.0.0.alpha1+ / LibreOffice Community
Build ID: d86889978d7caa4ac82eb4ede226c7f2561c8607
CPU threads: 8; OS: Linux 5.12; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 26 May 2021
Comment 5 Timur 2021-05-28 08:53:14 UTC
Also no repro Win7 LO 7.2+ Skia. Old trick, profile, maybe.
Comment 6 QA Administrators 2021-11-25 05:22:31 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2021-12-26 04:22:07 UTC
Dear Regina Henschel,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp