Bug 133009 - LibreOffice unusable (nearby freeze) after undo caused by another image being placed on first anchored to the second page
Summary: LibreOffice unusable (nearby freeze) after undo caused by another image being...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.7.2 release
Hardware: All All
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace, perf
Depends on:
Blocks: Anchor-and-Text-Wrap
  Show dependency treegraph
 
Reported: 2020-05-13 17:45 UTC by Telesto
Modified: 2023-09-23 03:15 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file (980.48 KB, application/vnd.oasis.opendocument.text)
2020-05-13 17:45 UTC, Telesto
Details
Perf flamegraph (133.02 KB, image/svg+xml)
2020-08-30 16:31 UTC, Buovjaga
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-05-13 17:45:25 UTC
Description:
Semi hang/freeze after undo of pasting an image with caption

Steps to Reproduce:
1. Open the attached file
2. Scroll to the second page
3. Select the frame
4. CTRL+X
5. Place the cursor after the yellow marking on pag 2
6. Paste -> Images/frame ends up at pag 1
7. CTRL+Z -> LibreOffice isn't usable anymore; it's possible to quite

Actual Results:
Have to quite document editing/unusable

Expected Results:
Should behave normally?


Reproducible: Always


User Profile Reset: No



Additional Info:
Found in
Version: 7.0.0.0.alpha1+ (x64)
Build ID: f9790da286f2d2fa47f1748f8cfa6172c6622ca3
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win; 
Locale: nl-NL (nl_NL); UI: en-US
Calc: threaded

and in
3.5.7.2
Comment 1 Telesto 2020-05-13 17:45:43 UTC
Created attachment 160771 [details]
Example file
Comment 2 Telesto 2020-05-13 17:46:29 UTC
The file will crash 6.4 (but should be fixed with 6.4.4)
Comment 3 Telesto 2020-05-13 17:49:08 UTC
Cause: bottom image on pag 1 is anchored to the second page..
Should this be allowed at all; anchor on a different page compared to the image/shape/object?
Comment 4 Durgapriyanka 2020-05-13 20:14:50 UTC
The file crashes when I try to open in 

Version: 6.4.0.0.alpha1+ (x86)
Build ID: ec7374ff84c71edfbb30d6e4dc5b486b6df7107f
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-11-10_21:37:30
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded
Comment 5 Telesto 2020-05-13 20:56:37 UTC
(In reply to Durgapriyanka from comment #4)
> The file crashes when I try to open in 
> 
> Version: 6.4.0.0.alpha1+ (x86)
> Build ID: ec7374ff84c71edfbb30d6e4dc5b486b6df7107f
> CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render:
> default; VCL: win; 
> TinderBox: Win-x86@42, Branch:master, Time: 2019-11-10_21:37:30
> Locale: en-US (en_US); UI-Language: en-US
> Calc: threaded

See comment 2 (fixed)
Comment 6 Telesto 2020-05-14 08:00:10 UTC
@Regina
Out of curiosity. Is it allowed to have image anchor (to character) on a different page compared to the image itself? The sample file illustrates it's possible.

However anchoring to paragraph is quite resistant against something like this happening, as far my observation goes.
Comment 7 Buovjaga 2020-08-30 16:31:37 UTC
Created attachment 164884 [details]
Perf flamegraph

Arch Linux 64-bit
Version: 7.1.0.0.alpha0+
Build ID: d784e711c102f204552c3c816636da01b1085f61
CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: kf5
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 29 August 2020
Comment 8 Roman Kuznetsov 2021-09-22 19:45:22 UTC
still rerpo in

Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: a9cc066a86c6bd3423c5802c5a4eded55a50c754
CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: ru-RU
Calc: CL
Comment 9 QA Administrators 2023-09-23 03:15:37 UTC
Dear Telesto,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug