Bug 156290 - In Calc/Win11, copying any cell hangs with 100% CPU (not corrupt user profile)
Summary: In Calc/Win11, copying any cell hangs with 100% CPU (not corrupt user profile)
Status: RESOLVED DUPLICATE of bug 153131
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.5.4.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-15 02:35 UTC by Barry L. Kramer
Modified: 2023-09-13 07:00 UTC (History)
3 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 Barry L. Kramer 2023-07-15 02:35:50 UTC
Description:
Running Calc from the Windows shortcut:
1. A blank sheet appears normally. Or, open any file.
2. Highlight and copy any cell.
3. Try to click on another cell.
--> Calc always hangs and CPU goes to 100%.  It never becomes responsive and must be right-click closed from the taskbar.

On the Internet, I have seen a number of reports about this that indicate it is either a Java problem or a corrupt user profile. I have followed the instructions for deleting and recreating a new user profile and it does not help However, if Calc is run From the command line using SCALC, even with the same user profile, the problem does not occur.  The following is my workaround for getting Calc to run without crashing: from a CMD prompt:

C:>"C:\Program Files\LibreOffice\program\scalc.exe" -env:UserInstallation=file:///c:/Users/blk/appdata/roaming/libreoffice/4/user

Any UserInstallation= will work to avoid the problem.  In fact, just running from a command prompt with no parameters at all using scalc.exe avoids the hang.  It only happens with the windows shortcut to the app that causes the problem. It just points at the default location.

Uninstalling and reinstalling Java will not help.



Steps to Reproduce:
See above Description.

Actual Results:
Software hang.

Expected Results:
No hang, such as when started using scalc.exe


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.5.4.2 (X86_64) / LibreOffice Community
Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded


Edition	Windows 11 Home
Version	22H2
Installed on	‎2/‎22/‎2023
OS build	22621.1992
Experience	Windows Feature Experience Pack 1000.22644.1000.0


Processor	AMD Ryzen 7 5700U with Radeon Graphics            1.80 GHz
Installed RAM	8.00 GB (7.35 GB usable)
System type	64-bit operating system, x64-based processor
Pen and touch	No pen or touch input is available for this display


Java Version 8 Update 371 (build 1.8.0_371-b11)
Comment 1 Barry L. Kramer 2023-07-15 02:56:28 UTC
Not sure, but this could be a duplicate of Bug 153131 but on a different system and OS. The problem looks similar, but I didn't see it when I first did the search for this problem existing already.
I also tried this with Clipboard History turned off. No effect.
Also, clarifying: this problem did not exist when I first installed Calc and Java. It started appering on an update of either windows or Java or Calc, but I do not know the update history to identify in which update it started.
Java 371 is visible and enabled in Calc.
Comment 2 ysui2022 2023-08-10 04:48:50 UTC
can't reproduce with
Version: 7.5.4.2 (X86_64) / LibreOffice Community
Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6
CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded
Comment 3 ericbresslermd 2023-08-13 20:15:07 UTC
Using the command prompt with this command as suggested by Barry Kramer did prevent the hanging from using Copy and Cut on my system.

"C:\Program Files\LibreOffice\program\scalc.exe"

The -env:UserInstallation= etc. did not work; fatal error as user installation could not be completed. 

Of course it's a clumsy workaround to have to use the command prompt. I sure would appreciate some brilliant coder figuring out how to fix this bug and include the fix in an update to Libre Office!
Comment 4 Buovjaga 2023-09-13 07:00:18 UTC

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