Bug 160455 - LibreOffice Writer crashes when hitting Ctrl+F
Summary: LibreOffice Writer crashes when hitting Ctrl+F
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
24.2.1.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-01 12:21 UTC by wilmargutierrezpelaez
Modified: 2024-04-13 18:48 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description wilmargutierrezpelaez 2024-04-01 12:21:31 UTC
Description:
I'm composing my very first document on my brand new ASUS Zenbook UX3404VC.
The original operating system language would be German (I'm based in berlin, Germany), but I changed it to English during the setup.
The document language is Spanish (Colombia).


Steps to Reproduce:
1. I hit Ctrl+F to try and find/replace a word. Nothing happened (I might have overlooked the search text field to the lower left side of the screen), so I hit it again. After a few seconds the app. crashed. 
2. I opened it again and loaded my file: unsaved changes were lost. 
3. I repeated the same steps again. This time I did see the text field.
4. I hit escape to dismiss the search text field.
5. I hit Ctrl+F again a couple of times. The search text field didn't show up this time. The app. crashed again after a few seconds.

Actual Results:
The application crashes and the unsaved changes are lost.

Expected Results:
The application does not crash by hitting Ctrl+F; unsaved changes are not lost.


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-GB
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
CPU threads: 20; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: en-GB (en_GB); UI: en-GB
Calc: CL threaded
Comment 1 m_a_riosv 2024-04-01 12:36:29 UTC
Please test in safe mode, Menu/Help/Restart in Safe Mode
Comment 2 wilmargutierrezpelaez 2024-04-01 12:51:40 UTC
I don't manage to reproduce the issue in safe mode.
Comment 3 m_a_riosv 2024-04-01 12:58:36 UTC
Then, in the window about Safe Mode, you can clean the profile, test with the options to Reset to factory options, if the first doesn't work then use the second.

Perhaps some kind of corruption in the user profile has happened, but is really difficult to find how that is was so.
Comment 4 wilmargutierrezpelaez 2024-04-01 16:35:37 UTC
Hello,

thank you very much for your support. Just wanted to let you know that I tried the profile clean-up, as suggested, but the issue persists.

It would have been a bit weird if the cause were to be found in my profile, since, as mentioned, it was my very first file, and after just a few hours of edition. I installed LibreOffice literally a few minutes before that first file. Anyway. I just have to avoid using search & replace :(
Comment 5 m_a_riosv 2024-04-02 00:01:34 UTC
Please then try disabling Skia
Menu/Tools/Options/LibreOffice/View
Comment 6 Armondo Lopez 2024-04-13 18:48:05 UTC
I was unable to reproduce the same behavior as you in

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

or 

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded