CLCL is a clipboard manager. When it is running, LibreOffice often freezes for several minutes when I try to call Copy or Paste operation. Not each time, but about 90%. If I exit CLCL I do not experience freezes anymore. One might think it's a CLCL's problem, but it happens only with LibreOffice, all other applications work perfectly with CLCL running.
Sorry, didn't notice that the "Version" field is "earliest affected". Unfortunately I cannot tell when it started, but long ago, many of the 4.x versions definitely had this problem too.
0% freeze for me with CLCL running. Win 7 Pro 64-bit, Version: 5.1.2.2 (x64) Build ID: d3bf12ecb743fc0d20e0be0c58ca359301eb705f CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Locale: fi-FI (fi_FI) Version: 5.2.0.0.alpha1+ Build ID: 3d27afd26f7b85c46a7c7d08498000b9dbcea1c8 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-05-09_02:42:15 Locale: fi-FI (fi_FI)
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Yes, I update LO from time to time but the issue is still there. Just reproduced it in 5.3.3.2 x64. The problem is, it cannot be reproduced reliably (like, do this, do that, and here you've got it). Sometimes it may work flawlessly for half an hour, sometimes it hangs at the very first attempt on any clipboard operation. Sometimes it's LO that hangs, sometimes it's CLCL that hangs, or even the target application I tried to paste the copied text into (it could be CLCL hook that hangs the target application, though). Another thing I completely forgot about is that I'm using not a downloadable binary from the official CLCL site but compiled it from sources (with minor changes to make it more Unicode-friendly by default), so it might also affect the behavior. I need to re-check with the stock CLCL but I keep forgetting to do that...
This bug may stay open but I'm afraid it's of no use since Buovjaga didn't reproduce and that os not widely used. So I set back to Needinfo for submitter to add some reproducible steps or new info. If you don't get Crash Report, and sometimes there's no in Windows - I guess you'd mentioned it if it were - you may use procdump (part of free and useful Sysinternaly Suite) during LO run in order to get a dump (soffice.bin.dmp). How: - run procdump manually after LO start (path-to\SYSINTERNALSSUITE\procdump.exe soffice.bin -h path-to\soffice.bin.dmp) for reproducible bugs like this one, OR - via simple batch file like attachment 129814 [details], that is used instead of LO icon to start LO, for intermittent bugs (which seems to be the case here). You may upload that crash dump or do it yourself: - analyze dump with WinDbg configured per https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg (set "Symbol File Path") - attach here as an attachment result of "!analyze -v" command in WinDbg (that's "backtrace") - if "!analyze -v" is empty, which comes after "ntdll!NtTerminateProcess" error, go with "kb" that prints stack trace and "~* kp" to dump the whole stack.
Not to forget, there are a number of nasty bugs with paste like Bug 46406 or Bug 107515. This may be related or not. Please write your OS version.
Konstantin: which LibreOffice applications do you use when it freezes? Writer, Calc..?
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180129
Created attachment 139635 [details] Crash dump analysis I'm terribly sorry for disappearance. I just did not have any time for proper bug maintaining. I have a custom-built CLCL, so it might have something to do with it. I also have many other programs running, each of them might have some effect too. So to make the test most useful I'd have to run a virtual machine or something with more or less clean environment, with original CLCL, and reproduce the problem there, but I didn't get time for that. Also, the bug is not always reproducable, so by the Murphy's Law when I try to get it deliberately it does not show, but then it hangs just when I really need to do some work, and do it right now, so I just restart the app, cursing at it and making myself a note to definitely process that bug properly next time... To reply the previously asked questions: My OS is Windows 7 SP1 64-bit. Specific LibreOffice applications I've experienced the problem with, are Writer and Calc, but I just don't use other apps, so it just might be they are all affected. Finally, I installed LO 6.0.0.3 64-bit and reproduced the problem in Writer, so I finally took the crash dump. I attached the "!analyze -v" output here. I kept the crash dump, so I can upload it too if required.
Please write steps. When you say "I try to call Copy or Paste operation" is CLCL used and how? Since this is specific, please find some time to try with regular CLCL so that others can reproduce.
CLCL is just running. I believe it uses hooks or some similar technique to monitor for clipboard, keep its history and (if requested by user) bring back one of the earlier contents into the clipboard. In my scenario I do not actively interact with CLCL in any way, just let it do its silent work. I don't have stable reproduction scenario, but what I generally do, is: open some document in LibreOffice (normally, a DOC file), select some text, copy it into clipboard, switch to another application, paste there, copy something from there, switch back to LO and paste, copy-paste within the same LO document, copy several times different parts of text without pasting anywhere... that kind of thing. Sooner or later, after one of the Ctrl+C or Ctrl+V keypress LO suddenly freezes, interface does not react to any input, and after several seconds Windows pops up with "Application does not respond". If I wait long enough (several minutes), it may unfreeze and continue to work normally, but then freeze again when I try to use clipboard next time. During the freeze, CLCL itself is also non-responding. If I was using another application to copy from or paste to, aside from LO, that application may freeze as well. I would have thought it the problem of CLCL, but as I described in the first post, it happens only with LibreOffice. All the same applications work flawlessly when no LO is running. I'll try to run the original CLCL to check if it's going to change anything (although I suspect it won't; all I did was just recompile the project as Unicode instead of ANSI, and with default settings also configured to support Unicode better).
Attempted to extract steps: 1. open some document in LibreOffice (normally, a DOC file) 2. select some text 3. copy it into clipboard 4. switch to another application 5. paste there 6. copy something from there 7. switch back to LO and paste 8. copy-paste within the same LO document 9. copy several times different parts of text without pasting anywhere Sooner or later, after one of the Ctrl+C or Ctrl+V keypress LO suddenly freezes, interface does not react to any input and after several seconds Windows pops up with "Application does not respond". If I wait long enough (several minutes), it may unfreeze and continue to work normally, but then freeze again when I try to use clipboard next time.
Buovjaga, please use procdump or WinDbg when you test it. Or always :) We can't say whether CLCL has an influence or not. Because frequent copy+paste may freeze LO anyway. These are long-standing nasty bugs that are hard to pinpoint.
I cannot reproduce with the steps from comment 12 and CLCL running. Note that comment 12 was just me prettifying Konstantin's explanation. Win 10 64-bit Version: 6.0.0.3 (x64) Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: fi-FI (fi_FI); Calc: group
Than we can only ask Konstantin to try both his and original CLCL running always with free procdump path-to\SYSINTERNALSSUITE\procdump.exe soffice.bin -h path-to\soffice.bin.dmp
Hello, I am another user of CLCL and this bug is driving me nuts too ! I am using CLCL 2.0.3 (official binary) on a Windows 7 64-bit SP1. For me the problem is systematic. Here's how it happens: - I have LibreOffice Writer opened, with a document I am working on - in another application, I copy some content (CTRL+C); it can be two lines of text of an image, the result is the same - when I switch to Writer to paste the content, it hangs before I even have a chance to do CTRL-V. The freeze can last from 15 seconds to 60 seconds - once it un-freezes, I can do CTRL-V and the content is pasted into the document Additional notes: - Writer does NOT crash - the freeze seems to start a couple of seconds after the copy operation (not at the exact second the copy was done) Let me know if you need additional information.
(In reply to Timur from comment #15) > Than we can only ask Konstantin to try both his and original CLCL running > always with free procdump > path-to\SYSINTERNALSSUITE\procdump.exe soffice.bin -h path-to\soffice.bin.dmp Leo442: can you try this?
Created attachment 142235 [details] Dump of soffice.bin performed with procdump tool Here's the dump as requested
And here's the Procdump output : > procdump.exe soffice.bin -h soffice.bin.dmp ProcDump v9.0 - Sysinternals process dump utility Copyright (C) 2009-2017 Mark Russinovich and Andrew Richards Sysinternals - www.sysinternals.com Process: soffice.bin (7964) Process image: C:\Program Files\LibreOffice\program\soffice.bin CPU threshold: n/a Performance counter: n/a Commit threshold: n/a Threshold seconds: 10 Hung window check: Enabled Log debug strings: Disabled Exception monitor: Disabled Exception filter: [Includes] * [Excludes] Terminate monitor: Disabled Cloning type: Disabled Concurrent limit: n/a Avoid outage: n/a Number of dumps: 1 Dump folder: C:\Procdump\ Dump filename/mask: soffice.bin Queue to WER: Disabled Kill after dump: Disabled Press Ctrl-C to end monitoring without terminating the process. [22:57:30] Hung Window: [22:57:30] Dump 1 initiated: C:\Procdump\soffice.bin.dmp [22:57:31] Dump 1 complete: 6 MB written in 0.4 seconds [22:57:31] Dump count reached.
Created attachment 142250 [details] Windbg analysis of the dump Produced an analysis of the dump with the advice in https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg#Producing_a_mini_dump
Dear Konstantin Vlasov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Sorry again for having disappeared. Too many things to do, too little time to do them... :-( I installed LO version 6.2.4.2 x64 shortly after your request, and since then I was working without prior exiting CLCL (as I was normally doing since I've noticed the bug). Unfortunately, it's not that often that I need to use LO, so the statistics is not plenty. Still, I can already tell that there is, if not a complete fix, then at least significant improvement. Out of 4 or 5 work sessions I've had, only once LO did freeze, but I don't know if it was the version 6.2.4 or not. Unfortunately my head was completely filled with the task at hand, so with a curse and barely any other thought I just quickly killed both LO and CLCL, restarted LO and continued my work. It was only much later that I remembered about the incident, and banged my head for not recording the event. Now I don't even remember which LO version was installed on that computer at that moment. I did update LO to the version 6.2.4 there, but somehow I completely forgot if the freeze happened before or after this update. Sorry about that, it would be very useful information. For now, I will keep watch on this problem and not forget to take a dump if it's reproduced. Is it OK to keep the bug open for a while, while I continue experimenting? If in a few weeks I don't reproduce the freeze I'll gladly call this fixed. As for checking for regression... I'll try to find time for it, but I cannot promise.
Well, we have Leo442, who was suffering from this last year. Would be interesting to hear his experience with 6.2.4.
LibreOffice 6.1.6.3 Calc Windows 10 Home 64 bit 8G Ram I do not use CLCL just normal Windows Clipboard. I get the same problem on Paste (Ctrl-V) I use the key shortcuts. Cannot reproduce consistently. Happens on more than one sheet. It freezes LibreOffice completely. I use Windows Task Manager to stop the process. Repair the file and carry on. I get this at least every other day. I save often and do not lose much work anymore. Please I need detailed explanation on how to produce useful "dump file" information for you to use. Thanks for the work you do. Ivan
(In reply to Ivan Williams from comment #24) > LibreOffice 6.1.6.3 > Calc > Windows 10 Home 64 bit 8G Ram The version you use is too old to be relevant at this point of the report. Please try with version 6.3.0
I am the same as the above poster. Don't know what CLCL is never used it. But LibreOffice calc regularly - daily, hourly freezes when doing CNP functions. In prior releases of Libre Office it was isolated to only when i was editing the contents of an existing cell - IE: double clicking a cell and modifying the formula. If i tried to copy something from that formula and repaste it the whole program would freeze and would never recover requiring a task manager shut down. Finally I got sick of it and started using OO. Then I updated LibreOffice to 6.3.x and thought to give it another shot. Now its much worse. Instead of freezing only in this one specific situation, it is freezing randomly during CNP operations including just the copy and paste of an entire cell contents. This is actually going to drive me to buy excel again :)
(In reply to locrash from comment #26) > I am the same as the above poster. > > Don't know what CLCL is never used it. But LibreOffice calc regularly - > daily, hourly freezes when doing CNP functions. > > In prior releases of Libre Office it was isolated to only when i was editing > the contents of an existing cell - IE: double clicking a cell and modifying > the formula. If i tried to copy something from that formula and repaste it > the whole program would freeze and would never recover requiring a task > manager shut down. > > Finally I got sick of it and started using OO. > > Then I updated LibreOffice to 6.3.x and thought to give it another shot. > > Now its much worse. Instead of freezing only in this one specific situation, > it is freezing randomly during CNP operations including just the copy and > paste of an entire cell contents. > > This is actually going to drive me to buy excel again :) Like it says in the description, "CLCL is a clipboard manager". If you never used it, then your issue is not the same as described in this report. Please open a new report and copy and paste there the contents of your Help - About. This allows us to know more about your system.
(In reply to Buovjaga from comment #20) > Created attachment 142250 [details] > Windbg analysis of the dump > > Produced an analysis of the dump with the advice in > https://wiki.documentfoundation.org/ > How_to_get_a_backtrace_with_WinDbg#Producing_a_mini_dump It makes me think about one of bt retrieved in https://bugs.documentfoundation.org/attachment.cgi?id=157317 (from tdf#127547).
I had this problem in Open office for the past 1.5 years. I switched to LibreOffice and to night it also froze using ctrl V and never recovered. I have used OO for many years and the problem first began somewhere between 1 and 2 years ago. Hoped Libre was free from this but it isn't... Running Win10 fully updated. Have NO problems in Win7.
(In reply to David from comment #29) > I had this problem in Open office for the past 1.5 years. I switched to > LibreOffice and to night it also froze using ctrl V and never recovered. > > I have used OO for many years and the problem first began somewhere between > 1 and 2 years ago. > > Hoped Libre was free from this but it isn't... > > > Running Win10 fully updated. Have NO problems in Win7. David: please confirm that you are also running the CLCL clipboard manager from http://www.nakka.com/soft/clcl/index_eng.html
I am NOT running CLCL!
(In reply to David from comment #31) > I am NOT running CLCL! Then your comment is off-topic for this report.
Well try to look at it the other way around. If the freeze occurs WITHOUT CLCL installed the bug is probably not in CLCL...
Dear Konstantin Vlasov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Version: 7.2.5.2 (x64) / LibreOffice Community Build ID: 499f9727c189e6ef3471021d6132d4c694f357e5 CPU threads: 6; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win Locale: en-ZA (en_ZA); UI: en-ZA Calc: threaded