Bug 101103 - Fatal error and crash when attempt to delete a row
Summary: Fatal error and crash when attempt to delete a row
Status: RESOLVED DUPLICATE of bug 100764
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.1.5.1 rc
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2016-07-24 23:29 UTC by akurpanek
Modified: 2016-07-25 00:10 UTC (History)
12 users (show)

See Also:
Crash report or crash signature:


Attachments
Example table to reproduce error (11.15 KB, application/vnd.oasis.opendocument.spreadsheet)
2016-07-24 23:29 UTC, akurpanek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description akurpanek 2016-07-24 23:29:45 UTC
Created attachment 126389 [details]
Example table to reproduce error

+++ This bug was initially created as a clone of Bug #100764 +++

When attempting to delete a row, LibreOffice calc gives error message;
LibreOffice 5.1 - Fatal Error
multi_type_vector::position#1477:block position not found! (logical pos=18446744073709551605, block size=6, logical size=1048576)

After changing content of cell B4 from "=A4" to "=A4-B22" and deleting row 5,
LibreOffice popped up with the upper error message an crashed when I click the OK button in this error message.

LibreOffice did not crash when I change cell B4 to "=SUM(A4;B21*-1)".

Enable/Disable OpenCL has no effects.


System here is
Fedora 24 (64-bit), LibreOffice 5.1.5.1 
build ID: 5.1.5.1-1.fc24
Comment 1 akurpanek 2016-07-24 23:43:04 UTC
Rolling back to Version 5.1.3.2 Build-ID 5.1.3.2-6.fc24 resolve the issue.
Comment 2 Aron Budea 2016-07-25 00:10:33 UTC
The fix for bug 100764 is not yet in 5.1.5.1. Please test with 5.1.5.2, which will be out in a few days (around Thursday) here:
http://dev-builds.libreoffice.org/pre-releases/

I tested the example with 5.2.0.3 (which was released a few days ago, and has the fix), and got no fatal error, while I could reproduce the issue with 5.1.4.2.
The error should be gone in 5.1.5.2.

*** This bug has been marked as a duplicate of bug 100764 ***