Bug 107515 - LibreOffice hangs on paste
Summary: LibreOffice hangs on paste
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected)
5.0 all versions
Hardware: x86 (IA32) Windows (All)
: medium critical
Assignee: Not Assigned
: 129623 (view as bug list)
Depends on:
Reported: 2017-04-29 08:40 UTC by rdt
Modified: 2020-06-10 14:00 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

OO hangs debug (6.32 KB, text/plain)
2017-05-31 20:06 UTC, rdt

Note You need to log in before you can comment on or make changes to this bug.
Description rdt 2017-04-29 08:40:52 UTC
Hangs with paste, usually with formatted text from clipboard, but also when fast/multiple copying between table rows, colums or text lines in the same document.  In rare cases unhangs after a few minutes. It's very frustrating and makes LO practically unusable for me - I can not save the file every minute, I lost a lot of data :/
This bug is known for a few years ago and still exists! It was tested on many versions of OpenOffice, LibreOffice, so it seems the bug exist somewhere in core code.

Steps to Reproduce:
1. Copy text with attributes from any other application and paste into text document (serveral times)
2. Copy text from table row and paste (multiple and fast) to another row

Actual Results:  
Hangs, dies, not responding. Soffice.bin process must be killed to respawn.

Expected Results:
Only normal working..

Reproducible: Sometimes

User Profile Reset: Yes

Additional Info:

User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36
Comment 1 m_a_riosv 2017-04-29 14:38:02 UTC Comment hidden (obsolete)
Comment 2 rdt 2017-04-29 16:19:42 UTC
Tested on latest LO Build 6cd4f1ef626f15116896b1d8e1398b56da0d0ee1 - the same fack-up..
Comment 3 m_a_riosv 2017-04-29 21:29:20 UTC
I'm not able to reproduce the issue.
Comment 4 rdt 2017-04-29 22:19:44 UTC
Hm, I don't know why. Try to copy from Calc and paste multiple/fast to Writer some text, especially copy rows, cells, etc - generally, text with attributes.
It occurs randomly, but very often. With continuous work with text, 1-4 times at hour. We (I and my coworkers) have this bug on several computers (Intel I7, Xeon, PC/Laptop), Windows versions (7, XP - Polish/English) with OO/LO Polish/English language, many versions.
After upgrade to, it looks like it is less frequent, but  I noticed, LO work slower ;) 
I have a TaskManager memory dump of hanged soffice.bin process, 
if it can be helpful.
Comment 5 Buovjaga 2017-04-30 11:33:35 UTC
You could try getting a backtrace of the hang: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg

As it's a hang, you might have to input

~* kp

like mentioned here:

Here is the reference on kp: https://msdn.microsoft.com/en-us/library/windows/hardware/ff551943(v=vs.85).aspx
The k* commands display the stack frame of the given thread, together with related information.
p Displays all of the parameters for each function that is called in the stack trace. The parameter list includes each parameter's data type, name, and value.
Comment 6 m_a_riosv 2017-04-30 12:48:27 UTC
I can't, please attach a sample file to use as source for coopy.
Comment 7 tommy27 2017-05-06 15:28:46 UTC

please give feedback to comment 5

in the meantime status -> NEEDINFO
Comment 8 rdt 2017-05-31 20:06:25 UTC
Created attachment 133758 [details]
OO hangs debug
Comment 9 rdt 2017-05-31 20:09:55 UTC
OO hangs. The debug output is in atatchement. 
After upgrade to hang less, but performance is very poor (it decreases proportionally to working time, need to close OO ex. every hour)
Comment 10 Buovjaga 2017-06-01 07:48:24 UTC
(In reply to m.a.riosv from comment #6)
> I can't, please attach a sample file to use as source for coopy.

rdt: can you provide a sample file?
Comment 11 Timur 2017-07-06 11:57:37 UTC
Backtrace with WinDbg is good when you expect crash/hang. 
But for not easily reporoducible problems, there are alternatives:
- remember to run procdump manually after LO start (path-to\SYSINTERNALSSUITE\procdump.exe soffice.bin -h path-to\soffice.bin.dmp) OR
- run LO via simple batch file like attachment 129814 [details], that is used instead of LO icon to start LO, for intermittent bugs like this one
Comment 12 Timur 2017-11-07 17:33:35 UTC
This one was Needinfo for a long time without exact repro steps and sample file. 
It's not useful to keep it open. Bug 46406 was closed for the same reason, no repro steps. Although problems are evident. 
If you provide required, feel free to set back to Unconfirmed.
Comment 13 Timur 2020-06-10 14:00:36 UTC
*** Bug 129623 has been marked as a duplicate of this bug. ***