Created attachment 98380 [details] showcase: two worksheets, one with named cells, the other referring to them Problem description: Steps to reproduce: 1.a. Open the attached showcase ods file 2. Go to the first worksheet, select name editing and change the ranges "one" and/or "two" - e.g. let them point to row 35 instead of 34 3. Apply changes, check the ranges actually changed 4.a. Save the document. Libreoffice crashes. 4.b. Go to the second worksheet. Libreoffice crashes. 5. Reopen Libreoffice. It asks to restore the document, do so and see the document restored to (just) before changing the named range(s). Alternative to 1: 1.b.1. Create a Spreadsheet document with two worksheets A and B. 1.b.2. In A, select two cell ranges and Define Names for each one. 1.b.3. In B, refer to them [using the formula SUMPRODUCT - don't know if this is neccesary] Environment: Libreoffice 4.2.3-3 from the Archlinux repositories. I think it already appeared with 4.2.2-2 from the same repo. Occurs even after deleting the userprofile ~/.config/libreoffice/4 Current/Expected behavior: Instead of being able to change the range of a Named cell range, Libreoffice crashes. References: Might or might not be related to https://www.libreoffice.org/bugzilla/show_bug.cgi?id=75741 Operating System: Linux (Other) Version: 4.2.3.3 release
Crash reproduced with attached .ods LO Version: 4.2.3.3 Build ID: 420m0(Build:3), Ubuntu Studio 14.04 x86_64. I tried twice without reproducing it from empty document and simple data: 2 columns with 1,2,3,4,5 in sheet A and SUMPROD(one;two) in sheet 2. One and Two zones from 1 to 4 first, and one modified to 1 to 5 --> no crash when saving.
On pc Debian x86-64 with master sources updated yesterday, I don't reproduce the crash. I put it as a dup of fdo#75741 however, if you can reproduce this with a daily build from master sources (see http://dev-builds.libreoffice.org/daily/master/) or prerelease 4.2.4, see http://www.libreoffice.org/download/pre-releases/, don't hesitate to reopen this tracker. *** This bug has been marked as a duplicate of bug 75741 ***
Confirm bug for 4.2.0.4 on Windows 7 Fixed in 4.2.4.1 pre-release on Windows 7 Fixed in 4.3.0 alpha1 on Windows 7