Created attachment 122963 [details] A problematic spreadsheet after shaving In document attached, select cells H23:P23 and drag the formulas down to row 27. The cells changed display empty and need F9 to reappear. I use a 32-bit Core Duo, but an AMD64 system I checked had this problem too. I have an Ubuntu Trusty, with "deb http://ppa.launchpad.net/libreoffice/ppa/ubuntu trusty main" in apt's sources. If I not misread my apt-get history log, the problem appeared in "5.0.5~rc2-0ubuntu1~trusty1" and is still present in "1:5.1.0~rc3-0ubuntu1~trusty0". I recall that previous version "5.0.4~rc2-0ubuntu1~trusty1" didn't have it. Disabling OpenCL and Software Interpreter doesn't help.
Created attachment 122964 [details] Obtained with --backtrace, after a hang. Another bug, much less reproducible, is that LO can crash or hang when dragging these formulas down one row a time. I attached a backtrace.
Hi @mjnowakowski, thanks for reporting. Your sample file has Menu/Tools/cells conten/Autocalculate disable. But there is a bug because, those empty cells must have the same value of the copied cells, what can be seen with copying instead dragging.
Thanks @m.a.riosv, do you mean Data -> Calculate -> AutoCalculate? I think I never messed with this setting, but it helps! I see the values being the same after copying (formulas are correct, just the values are wrong), but only when this AutoCalculate is off. It seems that my backtrace is quite easy to reproduce this way: disable AutoCalculate Select H23:P23 Copy it to H24:P24, then to H25:P25, then to to H26:P26 and finally to H27:P27 Select H23:P23 again Drag the formulas down to row H27:P27. Here LO crashes for me reliably.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
No crash in 5.1.6.2 for me, but I'm on a 64-bit machine now.
** Please read this message in its entirety before responding ** 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
draw down formula: works as expected with 5.4.7.2 (x64) - empty cells with autocalculate off, - correct results with autocalculate on, crashes: - not tested
steps from comment #3: disable AutoCalculate - ok, Select H23:P23 - ok, Copy it to H24:P24 - ok, then to H25:P25 - ok, then to to H26:P26 - ok and finally to H27:P27 - ok Select H23:P23 again - ok Drag the formulas down to row H27:P27 - ok. Here LO crashes for me reliably. - no crash, steps from comment #7: draw down formula: works as expected with 5.4.7.2 (x64) - still ok with 6.4.0.2 winx64, - empty cells with autocalculate off - still ok with 6.4.0.2 winx64, 'zeros' - correct results with autocalculate on - still ok with 6.4.0.2 winx64, results in H27, L25:L27, col.M, col.N, col.O, P27, crashes: - no crash with script from c#3, see above, tested with: Version: 6.4.0.2 (x64) Build ID: 08d19fecdc7a2298d051e19cfdb7c35544855fc3 CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win; Locale: de-DE (de_DE); UI-Language: en-US Calc: thus wfm 'til somebody finds any misbehaviour e.g. in an 32bit installation? reg. b. P.S. no crash with 4.1.6.2, repro crash with: Version: 5.0.0.1 (x64) Build ID: 9a0b23dd0ab9652e0965484934309f2d49a7758e Locale: de-DE (de_DE) thus setting first affected to 5.0.0.1 (not offered, taken 5.0.0.5), tested with x64, thus setting HW to all, tested with win, thus setting OS to all, P.S.II. 98009 wrong calculations avoidable by turning off openCL, this bug 98159 crash not avoidable by any seting for openCL, thus no or 'low' 'relation'?
sorry forgot: on crash sometimes error: 'SEH Exception: Access Violation!'