![]() Test to see if the bug is still present with the latest version of LibreOffice from If you have time, please do the following: We'd really appreciate your help in getting confirmation that the bug is still present. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. There have been thousands of bug fixes and commits since anyone checked on this bug report. 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. Dump 1 complete: 6 MB written in 0.4 seconds Press Ctrl-C to end monitoring without terminating the process. Process image: C:\Program Files\LibreOffice\program\soffice.bin Sysinternals - Process: soffice.bin (7964) ProcDump v9.0 - Sysinternals process dump utilityĬopyright (C) 2009-2017 Mark Russinovich and Andrew Richards 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). All the same applications work flawlessly when no LO is running. ![]() I would have thought it the problem of CLCL, but as I described in the first post, it happens only with LibreOffice. If I was using another application to copy from or paste to, aside from LO, that application may freeze as well. 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.ĭuring the freeze, CLCL itself is also non-responding. 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". 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. In my scenario I do not actively interact with CLCL in any way, just let it do its silent work. 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. I kept the crash dump, so I can upload it too if required.ĬLCL is just running. I attached the "!analyze -v" output here. 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.įinally, I installed LO 6.0.0.3 64-bit and reproduced the problem in Writer, so I finally took the crash dump. 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.Īlso, 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. I also have many other programs running, each of them might have some effect too. I have a custom-built CLCL, so it might have something to do with it. I just did not have any time for proper bug maintaining. 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. attach here as an attachment result of "!analyze -v" command in WinDbg (that's "backtrace") analyze dump with WinDbg configured per (set "Symbol File Path") You may upload that crash dump or do it yourself: via simple batch file like attachment 129814, that is used instead of LO icon to start LO, for intermittent bugs (which seems to be the case here). run procdump manually after LO start (path-to\SYSINTERNALSSUITE\procdump.exe soffice.bin -h path-to\) for reproducible bugs like this one, OR ![]() 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 (). So I set back to Needinfo for submitter to add some reproducible steps or new info. 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.
0 Comments
Leave a Reply. |