Bug 129711 - Unresponsiveness when deleting a sheet
Summary: Unresponsiveness when deleting a sheet
Status: RESOLVED DUPLICATE of bug 119650
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: perf
Depends on:
Blocks: Sheet
  Show dependency treegraph
 
Reported: 2019-12-31 16:47 UTC by Telesto
Modified: 2022-04-08 09:52 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Flamegraph (139.09 KB, application/x-bzip)
2019-12-31 23:13 UTC, Julien Nabet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2019-12-31 16:47:26 UTC
Description:
Unresponsiveness when deleting a sheet

Steps to Reproduce:
1. Open attachment 144526 [details] (bug 123417)
2. Select Sheet 4
3. Sheet -> Delete sheet

Actual Results:
Unresponsive

Expected Results:
Fast & quick removal of the sheet in question


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 42a1a1c6b91907f81e15066ffab219411f18c4db
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: GL; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL
Comment 1 Xavier Van Wijmeersch 2019-12-31 17:52:57 UTC
I can also reproduce with linux

Version: 6.5.0.0.alpha0+
Build ID: 8f25472d3de4f43cf594fa41ebfba2a1b01d4c9d
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: nl-BE (en_US.UTF-8); UI-Language: en-US
Calc: threaded
Comment 2 Telesto 2019-12-31 18:46:34 UTC
@Julien 
A flamegraph would be nice
Comment 3 Julien Nabet 2019-12-31 23:13:59 UTC
Created attachment 156865 [details]
Flamegraph

Here's a Flamegraph retrieved on pc Debian x86-64 with master sources updated today.
Comment 4 Julien Nabet 2020-04-12 15:56:12 UTC
It needed a Flamegraph not a bt=>remove wantBacktrace
Comment 5 Luboš Luňák 2022-04-08 09:52:02 UTC

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