Bug 130806 - Copying from Calc to PhpStorm uses 100% cpu and takes super long on Linux
Summary: Copying from Calc to PhpStorm uses 100% cpu and takes super long on Linux
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.0.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-20 12:29 UTC by Roman Stingler
Modified: 2020-11-24 04:18 UTC (History)
2 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 Roman Stingler 2020-02-20 12:29:26 UTC
I use Arch, latest packages (testing repo) and have following setup

Version: 6.4.0.3
Build ID: 6.4.0-2
CPU threads: 32; OS: Linux 5.5; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: CL

but If I copy a spreadsheet header and want to copy the text into 
PhpStorm the PC hangs the soffice.bin uses 100% cpu on one thread.
This doesn't happen when copying into gedit or sublime. And copying into one of those and then copying it into PhpStorm does work as expected.

I tried to change libreoffice with or without opencl, used openjdk and oracle java but these tries do not solve the problem.
Comment 1 Julien Nabet 2020-02-20 14:36:33 UTC
Since PhpStorm is not free, it's not possible to give a try.
The only way would be you build LO sources and retrieve a Flamegraph but I recognize it's quite some a request if you never did it.
Comment 2 Roman Kuznetsov 2020-04-26 00:12:38 UTC
Try build your own LibreOffice build, possible it's only Arch build problem.

When you make it, please write about retest result here.
Comment 3 QA Administrators 2020-10-24 05:13:09 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2020-11-24 04:18:30 UTC
Dear Roman Stingler,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp