Bug 137231 - Calc crashes when going back from cell XFD1 to cell A1048576
Summary: Calc crashes when going back from cell XFD1 to cell A1048576
Status: RESOLVED DUPLICATE of bug 133033
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.0.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-03 18:40 UTC by lino.fiorillo
Modified: 2020-10-04 14:00 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Fatal errox message (6.75 KB, image/png)
2020-10-03 18:42 UTC, lino.fiorillo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description lino.fiorillo 2020-10-03 18:40:23 UTC
Description:
A box error message occurs when I want to go back from the last cell of line 1 (cell XFD1)to A1048576 cell.
The message says "Libreoffice 7.0 - Fatal error. multi_type_vector::position#1774; block position not found! (logical pos=15999970, block size 1, logical size=1048576)

Steps to Reproduce:
1. Enable big worksheets (Tools/Options/Calc/Settings: 16m lines/16384 col)
2. In "Calc" module, go to XFD1 cell, using, for example, the shortcut CTRL+Right arrow
3. Press CTRL+left arrow;
4. Press CTRL+down arrow.

Actual Results:
A box error pops up:
Title: Libreoffice 7.0 - Fatal error
Message: multi_type_vector::position#1774; block position not found! (logical pos=15999970, block size 1, logical size=1048576)

Expected Results:
Going down to A1048576 cell, without any error


Reproducible: Always


User Profile Reset: No



Additional Info:
Once the box has appeared, it is necessary to press OK button. Then LibreOffice Calc automatically shuts down and you must restart LibreOffice.
Comment 1 lino.fiorillo 2020-10-03 18:42:23 UTC
Created attachment 166058 [details]
Fatal errox message
Comment 2 Roman Kuznetsov 2020-10-04 14:00:07 UTC
It was fixed for master.

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