Bug 124341 - Calc hangs on Format > Autoformat Styles
Summary: Calc hangs on Format > Autoformat Styles
Status: RESOLVED DUPLICATE of bug 115474
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: perf
Depends on:
Blocks:
 
Reported: 2019-03-27 08:46 UTC by atype
Modified: 2021-05-03 11:04 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description atype 2019-03-27 08:46:28 UTC 
Performing Format > Autoformat Styles and choosing any style on blank document causes Calc hang with high CPU usage.

To trigger the reported bug:
1) Open blank document
2) Edit > Select All
3) Format > Autoformat > Any style

Selecting only part of the document works as intended.
Comment 1 Telesto 2019-03-27 18:29:48 UTC 
Repro
Version: 6.3.0.0.alpha0+
Build ID: 20ea90a557b5bc744fd234e3a20ab1db484cf88b
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-03-22_03:21:58
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: threaded

and with 4.4.7.2

-> I leave it unconfirmed of now; not sure if this qualify's
Comment 2 Oliver Brinzing 2019-03-28 17:41:57 UTC 
already reproducible with AOO 4.1.5.

possible fix:
a warning could appear in case a huge number cells was selected
Comment 3 Buovjaga 2021-05-03 10:59:27 UTC 
Doesn't hang. Closing as WFM

Version: 7.1.2.2 (x64) / LibreOffice Community
Build ID: 8a45595d069ef5570103caea1b71cc9d82b2aae4
CPU threads: 2; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: fi-FI (fi_FI); UI: fi-FI
Calc: threaded
Comment 4 Buovjaga 2021-05-03 11:04:47 UTC 
Was wrong, this is a dupe and only seen with row-alternate shading (Box List styles...)

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