Description: Hi I received an XLSX spreadsheet from a client in the DRC (Congo). It opened ok, however it would often crash when I pressed Ctrl-C (copy to clipboard) on a field. Not always, but the sheet was a mishmash of data pasted from different places, so I'm assuming some of the fields contained weird fonts I don't have on my machine. All open spreadsheets would crash, I also received an out of memory message when I tried to bring up task manager. Windows ten then asked if I want to close calc, after which my computer returned to normal. I seem to remember my windows clipboard remained crashed however. Perhaps not. I was able to reopen the spreadsheet and start again. Steps to Reproduce: 1.Open a spreadsheet which uses a font you do not have (conjecture). 2.Select a field formatted using that font. 2.Copy field to clipboard. Actual Results: All instances of Calc stop responding and need to be terminated. Runaway memory usage. Expected Results: Nothing copied, perhaps warning message (OK). Field copied to clipboard using default font (Best). Reproducible: Sometimes User Profile Reset: No Additional Info: I eventually exported to CSV (preserve formulae), imported, and saved to ODS. This seems to have fixed the problem. Perhaps I could go straight to ODS without the CSV step, but it seemed safer to clear out all formatting.
OK I just had the crash on the converted ODS. I can confirm that the clipboard is not working. I opened a new Notepad++ doc, typed some text, selected it, copied, I am even able to cut, but it does not paste. Once I close Calc, the clipboard starts working again. Memory use seemed OK throughought.
Apologies, most of the above is a red herring. The bug is simple. 1) Open a blank spreadsheet. 2) Type the number 123 in A1. 3) Type the number 456 in A2. 4) Type =A1-A2 in another field, say C2. Result -333. 5) On C2, type F2, select the formula, and type Ctrl-C. 6) Calc not responding, and clipboard not pasting. Should I mention that the first time I tried it, I crashed, but after recovering a blank spreadsheet, it now works fine?
don't repro as described in Comment 2 in Version: 6.2.1.1 Build ID: 757c58e8cb70b2982843211a54750fb3cd79acd5 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded and please give us more clear steps if you'll can repro your problem
Having a similar issue to this. A simple document with 3 sheets, simple data, a few named ranges and formulae filled down various columns. I click in a cell with a formula I want to copy, click in the formula bar to select all the formula, try to Ctrl+C or Ctrl+X and the whole program becomes unresponsive then crashes. Version: 6.2.0.3 (x64) Build ID: 98c6a8a1c6c7b144ce3cc729e34964b47ce25d62 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-GB (en_GB); UI-Language: en-GB Calc: threaded
Hello Real, 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.
Dear Real, 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
Hi Apologies, the latest version of libreoffice as on 2019-03-25 appeared to have fixed the issue. I have just confirmed that the version 6.2.2.2 that I am currently on is also fine, thank you :D
(In reply to Real from comment #7) > Hi > > Apologies, the latest version of libreoffice as on 2019-03-25 appeared to > have fixed the issue. I have just confirmed that the version 6.2.2.2 that I > am currently on is also fine, thank you :D Thanks for retesting with the latest version. Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.