Please test in safe mode, Menu/Help/Restart in Safe Mode

Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)

(In reply to m_a_riosv from comment #1)
> Please test in safe mode, Menu/Help/Restart in Safe Mode

Hello M A Riosy and thanks for this prompt reply

Yes, I already did that (safe mode) before I reported the bug

Requested doc follows next

Best, Pa

Created attachment 195106 [details]
Calc file as Requested

Here FYC is the requested sample document

Because it will be public but yet is just one sheet in a huge Calc file documenting all my financial, energy use and CO2 producing activities for the last 5 years it took quite some time to extract and modify for viewing this duplicate page

You should be able to see v easily that the sum function is not working anywhere

eg try replacing the contents of a cell in a summed column with a new (different) numerical entry and you will see that the sum doesn't change

In the course of extracting this sheet from the master file I've also noticed another critical and v damaging bug which is:

The (almost essential) function allowing a formula attached to a cell to be dragged down a column so that the formula also applies to sequential cells

FYC I have highlighted this new error in this doc (at the foot)

Hope this is what need?

Here it is anyway

Two things.
-Menu/Data/Calculate - Autocalculate is disabled.
-Cells F36:G36 has an error formula.

Menu Data/Calculate/Recalculate Hard display several REF pbs.
Could you fix them and test again?

FWIW, I am under the impression that the crash reports linked in comment 0 have nothing to do with the report about SUM() somehow failing (which cannot be proved by attachment 195106 [details], considering that AutoCalculate is OFF and cell F36 has a #REF! error).

Additionally, attachment 195106 [details] seems saved with a different (newer) version than the crash links reported in comment 0.

Unfortunately, we need clearer explanations of these relations and reported symptoms.

Are the crashes still happening in newer versions of LO in your system?

Can you correct the formulas (to avoid the #REF! errors), set AutoCalculate to ON, then execute recalculate hard and review whether the result of SUM() still fails as initially reported?

Created attachment 195175 [details]
updated calc file for debugging

Thanks for yr response

Here FYI FYC are (I hope) full accounts of the requested 'clearer explanations of these relations and reported symptoms'
:

1) The basic (original as reported) bug right enough occurred when running the previous version of Libre Office (to the most recent update). As I said previously, the sheet is part of a set of multi-annual running accounts consisting of daily measurements taken of kWh of electricity use. 2 v simple formulas then allow me to calculate daily  electricity use (in kWh)  and daily CO2 emissions (in Kg). For statistical purposes I also need to be able to keep a running log of daily use and daily emissions, monthly use and monthly emissions to date and projected annual total (for both kWh and CO2). I have been successfully doing this for many MANY years now using Calc and for all that time I have NEVER had a problem just dragging the 2 formulas down from the previous day's results to get today's result. It must have been so long ago that I'm afraid I can't recall whether or when I turned Autocalculate on in order to do this. What I CAN quite DEFINITELY assure you of is that I PERSONALLY have *NEVER* turned it off

2) The bug as originally reported occurred when I had just closed the monthly summed account of kWh for June. In order to then start a new account for July I did EXACTLY what I have be doing TOTALLY successfully for many years in Calc (and for many years in MS Excel before that) - which is to merely create a *new* sum in the column for kWh (F in the attached doc) consisting of the sum of the 1st and 2nd days of the new month (in order to create a valid sum) and then drag it down through several blank cells below that BUT STOPPING ABOVE the (SUMMED) RUNNING TOTAL for the year. Obviously I then get a (very temporary) false running total because July is now double counted. But for many MANY years now all I do then is cut the sum for the running total for July from the column and paste it straight back into the monthly cell for July (in the by-the-month table below all the daily running sums)

3) The FIRST CRASH report you received  was *IMMEDIATELY* after I first tried to make that paste

4) At the time, I was running the previous version of LibreOffice

5) But I had performed this *very same operation* with ABSOLUTELY NO PROBLEM at all already 6 times this year using that particular version of Calc (and for many years before that using both that and previous previous versions)

6) So I recovered the doc, tried again and it crashed again

7) As you say, the initial crash reports were when I was running the previous version (on the 2nd of July):

020724 - The crash report was successfully uploaded.
You can soon find the report at:https://crashreport.libreoffice.org/stats/crash_details/d7a2824e-a111-4285-be19-29afbcb828e2

020724 - The crash report was successfully uploaded.
You can soon find the report at:
https://crashreport.libreoffice.org/stats/crash_details/8f980070-1fbf-4ec6-83ad-d7219d6a5d02


8) Thinking it might be something to do with the fact that I hadn't yet migrated to the new version of LibreOffice, I downloaded that, restarted the computer and tried again

8) I tried again *twice*, it crashed again *twice* ALWAYS on the same paste the sum operation

9) Here is the crash report (from always the same paste-the-sum operation) once running the new version and the request from you to report the bug:

https://crashreport.libreoffice.org/stats/crash_details/16a37987-bd97-4e83-bd47-1438e3e886ce

Please check the report, and if no bug report is connected to the crash report yet, open a new bug report at bugs.documentfoundation.org

10) So (somewhat painfully after finding my way around your bug reporting protocols) I created the bug report

11) So that is the answers to your question: Are the crashes still happening in newer versions of LO in your system?

12) Once you had asked me for the sample doc to help you work things out I had (as I already said) to go to quite some lengths to edit and redact the operational doc in question to render it suitable for public display

13) So that (together with the timeline described above) explains the apparent (IMHO not necessarily very critical) fact that: 'Additionally, attachment 195106 [details] seems saved with a different (newer) version than the crash links reported in comment 0.

14) It was in the course of preparing that doc that I noticed that the autosum function had apparently also malfunctioned

15) That is why that is reported as a noted addendum within the doc as sent, and *not* actually as the bug in the initial report

16) Thanks to your request to: 'Can you correct the formulas (to avoid the #REF! errors), set AutoCalculate to ON, then execute recalculate hard and review whether the result of SUM() still fails as initially reported? I have now done exactly that and

17) I have discovered that the supposed '#REF' issue was/is immaterial (merely a relic of the edited doc and now replaced with a hard number in the relevant cell in this new version)

18) It now looks very much as though somehow or other (??) Autocalculate got *turned off* in the course of those crashes, since I myself MOST CERTAINLY DID NOT TURN IT OFF (Is that remotely possible ? - I can think of no other explanation)

19) So that is now back working in this new version

20) LITERALLY NONE OF THE ABOVE distracts from the fact that the original bug (as reported) is STILL very much in place

21) To replicate it: in the *new* version of the file (*attached* here) you will find that using the (now working) Autosum function I have already created for you (in the vital column F for kWh) a *new* sum for the kWh used in the current first days of July

22) Cell F239 now reports (accurately) a sum of 49 kWh for those days and is represented in the formula bar as a function =SUM(F228:F236)

23) Therefore (as already mentioned) the running annual total (in cell F242) is actually a false total, as the 49 kWh in F239 is now double counted

24) Now TO REPLICATE THE CRASH: firstly cut cell F239 (you will notice F242 now reverts to the *true* annual running total (49 less than previously)

25) Secondly TRY PASTING THE CUT CELL (sum of F228:F236) into the destination cell
awaiting it:  F268 (July in the monthly breakdown table - left unshaded here for easy identification)

26) Get back to me if it doesn't crash. But it certainly crashes this end

27) Here FYI FYC are tonight's crash reports attempting that same operation yet again:

080724 (3) - The crash report was successfully uploaded
https://crashreport.libreoffice.org/stats/crash_details/246c1c76-8867-450a-b104-178f1d822ce6

080724 (2) - The crash report was successfully uploaded
https://crashreport.libreoffice.org/stats/crash_details/0c67a315-9feb-43b5-afca-478f08d2cb5c

080724 - The crash report was successfully uploaded
https://crashreport.libreoffice.org/stats/crash_details/d3e17fd8-a91e-48be-83e0-1cc417c45d93


28) SHOULD IT CRASH - I'll be amazed if it doesn't -  and you then recover the doc you will then almost certainly find (at least I did earlier this evening) that the figure 49 is now *most mysteriously* somehow now to be found in the *correct destination cell* (F268 - for kWh in July) but that *equally* mysteriously in the formula bar you will now find that it is showing the FALSE SUM of =SUM(F257:F265)


29) The bug reports are all showing up as a 'Unhandled C++ Exception'


30)Hopefully all this inf. and further detail is now sufficient for you to get to zero in and get to the bottom of whatever is causing this desperate bug (??


I hope so anyway !!

It would help if someone would test on OSes other than Windows; the STR are very simple.