Created attachment 65776 [details] Example document Problem description: I tried to delete 2 cells (A7:A8 in the sample). They contain formulas. - Cell A8 compute the SUM from A1 to A4: =SUMME(A1:A4) - Cell A7 compute the SUM from A1 to A4 minus A8 = SUMME(A1:A4)-A8 By deleting both cells with the formulas, LO will crash! Steps to reproduce: 1. Open a new spreadsheet 2. type any Numbers in the Fields from A1 to A4 3. count the SUM in one of the fields below 4. count antother/the same SUM minus the result of step 3 in the field below 5. Try to delete both fields at the same time! (Just by mark them and hit delete) Current behavior: LO crash! Expected behavior: delete the cells... Platform=Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:14.0) Gecko/20100101 Firefox/14.0.1
Thank you very much for your bug report, especially for the nice descriptions which steps to reproduce and the sample file! REPRODUCIBLE with LibreOffice 3.6.1.1 (Build ID: 4db6344), German langpack installed, on MacOS X 10.6.8 (Intel). I just open the reporter’s sample file, select both A7 and A8, hit delete key, select "clear all" in the dialog box, press "OK" -- crash. I will attach the log file for the crash. NOT reproducible with LibreOffice 3.5.6.2 (Build-ID: e0fbe70-dcba98b-297ab39-994e618-0f858f0) on the same machine, therefore added keyword "regression".
Created attachment 65868 [details] Crash log for bug 53710, LibO 3.6.1.1 on MacOS X 10.6.8
The crash log is very very similar to the one for bug 53364 - "Crash cutting or dragging block", so this may be a duplicate or at least a closely related bug. But I don’t mark it as a duplicate for now, because only a developer can tell if the bugs are really identical.
@Markus Mohrhard: Hello Markus, this is yet another Calc bug which seems related to the lifetime of cell broadcasters. Please take a look at it. The crash log is very similar to the one for bug 53364, which you are already investigating, so I add your e-mail address to the CC list of the present bug, too. It is possible that both bugs are identical, at least they seem closely related, so IMHO it makes sense that you take this one, too ... Thank you very much in advance!
(In reply to comment #1) > Thank you very much for your bug report, > especially for the nice descriptions which steps to reproduce and the sample > file! > > > REPRODUCIBLE with LibreOffice 3.6.1.1 (Build ID: 4db6344), German langpack > installed, on MacOS X 10.6.8 (Intel). > > I just open the reporter’s sample file, select both A7 and A8, hit delete key, > select "clear all" in the dialog box, press "OK" -- crash. I will attach the > log file for the crash. > > NOT reproducible with LibreOffice 3.5.6.2 (Build-ID: > e0fbe70-dcba98b-297ab39-994e618-0f858f0) on the same machine, therefore added > keyword "regression". Thank you for your nice words of welcome! Glad I can help this wonderful project... If I can help somehow please let me know!
(In reply to comment #5) > Thank you for your nice words of welcome! Glad I can help this wonderful > project... > > If I can help somehow please let me know! @Nils: Thank you for your nice offer! IMHO there is nothing left to do for us about this particular bug report. But LibreOffice always needs more QA volunteers -- which just means people who test LibreOffice and try to confirm bug reports (i.e., what I did with your present bug report). If you could take part in this process, even just for an hour now and then, this would be very much appreciated and really help the project. Please see http://wiki.documentfoundation.org/QA However, that page is a bit technical, and IMHO gives the wrong impression that QA work is complicated; in reality, everybody who can use LibreOffice and write precise descriptions for problems (something you definitely can do, as your description of this present bug shows ;-) can help. Therefore, if you are interested, even just a bit, drop me a note to bugs@eikota.de and I can try, if you want, to send you a short informal introduction to the QA process, also known as "bugwrangling" ;-)
definitely a duplicate *** This bug has been marked as a duplicate of bug 53364 ***