Bug 159650 - Double clicking on a cell containing Karasiewicz crashes LibreOffice Calc
Summary: Double clicking on a cell containing Karasiewicz crashes LibreOffice Calc
Status: RESOLVED DUPLICATE of bug 158945
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
24.2.0.3 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-08 23:17 UTC by gpapotti
Modified: 2024-03-01 00:58 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Empty sheet with Karasiewicz in a cell (9.28 KB, application/octet-stream)
2024-02-08 23:18 UTC, gpapotti
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gpapotti 2024-02-08 23:17:19 UTC
Description:
A spreadsheet containing the work Karasiewicz (with proper diacritics) crashes simply double-clicking on the cell.



Steps to Reproduce:
1. Open new calc
2. In any cell, paste the word:  Karasiewicz
3. Leave the cell
4. Double click on the cell
5. wait... BOOM!

Actual Results:
Calc closes.

Expected Results:
Select the cell content


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no
Comment 1 gpapotti 2024-02-08 23:18:22 UTC
Created attachment 192476 [details]
Empty sheet with Karasiewicz in a cell
Comment 2 raal 2024-02-08 23:38:05 UTC
Hello,

Thank you for filing the bug. For the test, could you rename your LibreOffice directory profile (see https://wiki.documentfoundation.org/UserProfile)  or run LibreOffice in safe mode (https://help.libreoffice.org/7.2/en-US/text/shared/01/profile_safe_mode.html) and give it a new try? Thank you
Comment 3 gpapotti 2024-02-11 10:51:28 UTC
Same result renaming user profile and repeating the test.
Comment 4 LeroyG 2024-02-11 21:00:02 UTC
(In reply to gpapotti from comment #0)
> A spreadsheet containing the work Karasiewicz (with proper diacritics)

I don't see the diacritics in the sample file.
Comment 5 gpapotti 2024-02-11 22:27:09 UTC
You are right, I overlooked the name (the word is a surname), it has no diacritics and provokes the bug.
Comment 6 Stéphane Guillou (stragu) 2024-02-27 06:34:53 UTC
Does not crash with:

Version: 24.2.0.3 (X86_64) / LibreOffice Community
Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Nor on Windows 11:

Version: 24.2.0.3 (X86_64) / LibreOffice Community
Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Please share the full version information copied from Help > About > LibreOffice.
If you see "UI Render: Skia/Vulkan", please:
* share your Skia log, copied from Tools ▸ Options... ▸ LibreOffice ▸ View
* see if it still crashes with Skia/Raster instead, by turning "Force Skia software rendering" on in the same dialog.
Comment 7 Stéphane Guillou (stragu) 2024-02-27 06:40:25 UTC
(In reply to Stéphane Guillou (stragu) from comment #6)
> Nor on Windows 11:
Version: 24.2.0.3 (X86_64) / LibreOffice Community
Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1
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
Comment 8 gpapotti 2024-02-27 12:07:39 UTC
I added a short video taken with Snaptool to show you hou to repro:
https://youtu.be/NoLsbAcqmSw
Comment 9 QA Administrators 2024-02-28 03:14:50 UTC Comment hidden (obsolete)
Comment 10 Stéphane Guillou (stragu) 2024-02-28 08:29:40 UTC
Thanks for the video, but I still can't reproduce.
Can you please paste here your full version information copied from Help > About LibreOffice? There's a button to copy it.

And please also try this:

(In reply to Stéphane Guillou (stragu) from comment #6)
> If you see "UI Render: Skia/Vulkan", please:
> * share your Skia log, copied from Tools ▸ Options... ▸ LibreOffice ▸ View
> * see if it still crashes with Skia/Raster instead, by turning "Force Skia
> software rendering" on in the same dialog.
Comment 11 gpapotti 2024-02-29 23:10:30 UTC
Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: it-IT (it_IT); UI: en-US

Calc: threaded
Skia log:
RenderMethod: vulkan
Vendor: 0x8086
Device: 0xa7a0
API: 1.3.235
Driver: 0.404.4032
DeviceType: integrated
DeviceName: Intel(R) Iris(R) Xe Graphics
Denylisted: no

With option "Force Skia software rendering" LibreOffice Calc DOES NOT crash.
Comment 12 gpapotti 2024-02-29 23:22:14 UTC
PS As you can see, I just updated libreoffice to the latest version, and problem persists. If I uncheck force software rendering it still crashes.
For me it's very simple to replicate:
I open a new Calc, in any cell I paste Karasiewicz, click on another cell, then double click on the cell with "Karasiewicz", everything freezes for about 5 seconds and then... crash.

Same problem also with other keywords; for example perdonare (means to forgive in italian), meaning, but not with elena (it's a name).
Really can't figure out where the problem can be...
Comment 13 gpapotti 2024-02-29 23:37:33 UTC
Ok, with sysinternalS debugview I got:
00000003	42.10389709	[17396] Failed vulkan call. Error: -4,QueueSubmit(queue, 1, &submitInfo, fence)
Hope it helps
GP
Comment 14 ady 2024-03-01 00:35:26 UTC
FWIW, recent tdf#158945 and tdf#158129 are also related to device device: 0xa7a0. Perhaps the attempts to solve those (which apparently failed there) might work here?? Even if not, in-common info could help narrow down the problem.
Comment 15 Stéphane Guillou (stragu) 2024-03-01 00:58:43 UTC
Thanks for the info, gpapotti.

Ady, you're right. Given this report and bug 158945 have essentially the same symptoms, let's tart with marking this as a duplicate and continue the conversation there.

*** This bug has been marked as a duplicate of bug 158945 ***