Bug 128946 - Libre Office Calc crashed with search in selected column
Summary: Libre Office Calc crashed with search in selected column
Status: RESOLVED DUPLICATE of bug 128313
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.3.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected
Depends on:
Blocks:
 
Reported: 2019-11-22 07:23 UTC by Konstantin
Modified: 2019-11-23 16:40 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample CSV which gives the crash (30.06 KB, text/plain)
2019-11-22 08:15 UTC, Konstantin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Konstantin 2019-11-22 07:23:53 UTC
Description:
Opened csv-file, selected column by press on column`s header, pressed Ctrl+H. Calc goes crashing from second press "Find Next". Using LibreOffice 6.3.3.2(x64) on Win 10

Steps to Reproduce:
1.Open csv-file
2.Select whole column
3.Press Ctrl+H
4.Fill "Find"
5.Press "Find Next" twice

Actual Results:
LibreOffice total crash

Expected Results:
Normal work)


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Mike Kaganski 2019-11-22 07:48:38 UTC
I can reproduce this:

1. In a new Calc spreadsheet, put 1 into B1
2. Click on B header to select B:B
3. Ctrl+H; put 1 into "Find:" box; "[x] Current selection only" is autoselected; search in: formulas (default)
4. Press "Find Next" (shows "Reached the end of the sheet")
5. Press "Find Next"

Calc hands - for some long time (~50 s in my testing); I couldn't reproduce a crash (a sample file might be needed?). But trying to close Calc afterwards seemed to hang Calc forever.

Tested with Version: 6.3.3.2 (x64)
Build ID: a64200df03143b798afd1ec74a12ab50359878ed
CPU threads: 12; OS: Windows 10.0; UI render: GL; VCL: win; 
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded

But can't reproduce a hang with Version: 6.5.0.0.alpha0+ (x64)
Build ID: e371baccb4da0d97794f6614c6362bd8e32ee32b
CPU threads: 12; OS: Windows 10.0 Build 18362; UI render: GL; VCL: win; 
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: CL

So possibly fixed in master -> reverse bibisect needed?

As a crash is mentioned in the report, please attach a sample CSV which gives the crash. Setting to NEEDINFO; please put back to UNCONFIRMED after attaching the file. Thanks!
Comment 2 Konstantin 2019-11-22 08:15:05 UTC
Created attachment 156024 [details]
Sample CSV which gives the crash

In this time i haved new trouble, when making screenshot with error window. My dispaly settings was reset to 1024*768 from standart 1920*1080. Screenshot taked with Joxi - joxi.ru/a2Xl74ZCw6Ppb2 (there is some artefacts because of display size was changed)
Comment 3 QA Administrators 2019-11-23 03:44:18 UTC Comment hidden (obsolete)
Comment 4 Mike Kaganski 2019-11-23 08:25:00 UTC
This is a clear duplicate of tdf#128925 - but I hesitate marking it that way, because of more information here.

The crash must be the result of out-of-memory condition. The second search takes about 6 GB memory for soffice.bin process; on my system with 16 GB memory, this doesn't crash.

Last win32-6.3 bibisect point (for https://git.libreoffice.org/core/+/13152ad88b24cadc836a829b4424a72a152ca9b1) already has the problem.

The problem has been *fixed* in master toward 6-4 (so 6.4 release will be already OK) in https://git.libreoffice.org/core/+/12eb32fccec16a436a6c3eca725b9d6d449f8e19.

Caolan, Xisco: should the change fixing this be backported to 6-3?
Comment 5 Mike Kaganski 2019-11-23 08:45:31 UTC

*** This bug has been marked as a duplicate of bug 128313 ***
Comment 6 Caolán McNamara 2019-11-23 15:19:19 UTC
I think we have a backport to the next 6-3
Comment 7 Mike Kaganski 2019-11-23 15:22:56 UTC
(In reply to Caolán McNamara from comment #6)

Of course; thank you!
Comment 8 Xisco Faulí 2019-11-23 16:40:28 UTC
(In reply to Caolán McNamara from comment #6)
> I think we have a backport to the next 6-3

https://gerrit.libreoffice.org/plugins/gitiles/core/+diff/66397e67829f2f502b9b6799dab16fa9a5390020%5E%21

it should be fixed in LibreOffice 6.3.4