Bug 136626 - Crash in BigPtrArray::Index2Block(...) after undoing the pasting of a document
Summary: Crash in BigPtrArray::Index2Block(...) after undoing the pasting of a document
Status: RESOLVED DUPLICATE of bug 134101
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.4.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Undo-Redo Clipboard
  Show dependency treegraph
 
Reported: 2020-09-09 21:32 UTC by Telesto
Modified: 2021-01-15 09:53 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["BigPtrArray::Index2Block(unsigned __int64)"]


Attachments
Example file (1.04 MB, application/vnd.oasis.opendocument.text)
2020-09-09 21:33 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-09-09 21:32:49 UTC
Description:
swlo!BigPtrArray::Index2Block (99% probability a dupe)

However, pretty small for the difference

Steps to Reproduce:
1. Open the attached file
2. CTRL+A
3. CTRL+C
4. CTRL+N
5. CTRL+V
6. CTRL+Z

Actual Results:
Crash

Expected Results:
No crash


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.1.0.0.alpha0+ (x64)
Build ID: e8b8e7be0b2ad693224cd94062a55610eb69df7e
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 1 Telesto 2020-09-09 21:33:03 UTC
Created attachment 165340 [details]
Example file
Comment 2 Aron Budea 2020-09-10 01:13:53 UTC
Version field has 4.4.0.3, but that version isn't mentioned in the description. Plus a crash report would've been nice.

https://crashreport.libreoffice.org/stats/crash_details/d74394f5-4140-490d-a81b-0991b303f42c

Confirmed in LO 7.0.0.3 / Windows.
Comment 3 Xisco Faulí 2021-01-15 09:53:30 UTC
Issue fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=b4365b985178e1866c74afd757a104aad1d405a9
Closing as dupe of bug 134101

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