https://bugs.documentfoundation.org/show_bug.cgi?id=158691

            Bug ID: 158691
           Summary: On copying multiple cells Calc goes into Not
                    Responding, locks up and freezes.
           Product: LibreOffice
           Version: 7.6.4.1 release
          Hardware: x86-64 (AMD64)
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Calc
          Assignee: [email protected]
          Reporter: [email protected]

Description:
Copying multiple cells causes Calc to not respond and memory use to increase
rapidly and appears would use all available memory given time. I close the
program before it goes over a Gig or so as I wasn't interested in causing OOM
errors on my OS. The Calc application CPU stays around 8-12%.

There are multiple ways to reproduce this issue. However, making a new
spreadsheet copying a 2x2 is enough to freeze it. There is no need to change
the cells or for a specific spreadsheet file. I just installed LibreOffice and
this laptop is brand new. I wouldn't expect problems like this.



Steps to Reproduce:
1. In the Windows search menu search "Offer suggested actions" and it should
take you to a setting in System > Clipboard. Toggle "Suggested actions" on
2. Open Calc and new file or existing file whatever you prefer.
3. Copy multiple cells or copy a whole row or copy a whole column.
4. Attempt any other action. Calc should be frozen and will go not responding
in a few minutes.
5. Check Task Manager and the Calc process memory usage will be climbing and
continue to climb. Careful, I don't not know the max it will climb. It could
cause OOM if left alone for too long. 
6. Stop Calc from task bar or kill the process from Task Manager.

Actual Results:
Calc stops responding and freezes

Expected Results:
Calc to copy cells to the Windows clipboard and continue to be responsive.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.4.1 (X86_64) / LibreOffice CommunityBuild ID:
e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1CPU threads: 20; OS: Windows 10.0 Build
22621; UI render: Skia/Raster; VCL: winLocale: en-US (en_US); UI: en-USCalc: CL
threaded

My system info.

Edition Windows 11 Pro
Version 22H2
Installed on ‎12/‎5/‎2023
OS build 22621.2792
Experience Windows Feature Experience Pack 1000.22681.1000.0

Troubleshooting steps I remember taking:
Safemode
Safemode disable hardware acceleration
Disable JRE
Multiple reboots
Install repair
Delete LibreOffice profile
Updating Windows and Laptop drivers (Just because)

This appears to be due to the Windows clipboard "Suggested actions" feature.
When I disabled that feature the issue is now resolved. 

Workaround:
In the Windows search menu search "Offer suggested actions" and it should take
you to a setting in System > Clipboard. Toggle "Suggested actions" off. It says
this is for getting suggestions for actions when you copy a date, time, or
phone number.

I found the workaround from the suggestions in this thread.
https://ask.libreoffice.org/t/calc-freezes-on-copy-nov-22-solution-recomendations-make-no-difference/87840/8

Request: Fix the compatibility issue between LibreOffice and Windows clipboard
features such as the "Suggested actions". It also seems the clipboard history
feature might affect LibreOffice as well based on other reports, but I didn't
test enabling that feature.

P.S this is my first bug report. I hope I am doing this correctly.
For the priority, I thought normal fits because of the high visibility to users
because Windows is setting "Offer suggested actions" is enabled by default. It
wasn't easy finding the answer and I could see new users giving up on
LibreOffice if this is their initial experience. The issue was starting to
disappoint me to switch to something else. Anyway, the clipboard feature is new
and I haven't been able to use it to comment on it's value, but it looks nice
from what I have seen. It is a shame I have to disable it for LibreOffice.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to