Bug 159593 - Crash in: SwFEShell::GetAnchorId() FORMATTING DIAGRAM
Summary: Crash in: SwFEShell::GetAnchorId() FORMATTING DIAGRAM
Status: RESOLVED DUPLICATE of bug 132810
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2024-02-06 10:22 UTC by Christopher Benson
Modified: 2024-02-22 15:59 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["SwFEShell::GetAnchorId()"]


Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Benson 2024-02-06 10:22:00 UTC
This bug was filed from the crash reporting server and is br-6e1bd497-bd89-49c2-ae18-b9be1755bfe6.
I was adding a diagram to a Writer document. I had dragged a template from the Insert Gallery sidebar and had just replaced all the text in the template. I wanted to complete the diagram by overlaying a colourful arrow. I thought I could do this by dragging an arrow from the Arrow subsection of the Insert Gallery sidebar. But this action just created a separate object consisting of just the arrow, placing it BEFORE and not ON TOP OF the existing diagram as I had wanted. When I realised I had created a separate unrelated object, I decided to remove the arrow and abandon the need for it. So I clicked the UNDO top-row toolbar icon, expecting it to UNDO my last action (Insert Arrow). But instead, UNDO left the new arrow in place and removed the whole older customised diagram. I attempted to UNDO the UNDO and salvage my diagram by clicking on the REDO toolbar item. It was the REDO click that caused the crash, initially evidenced only by the complete disappearance of the Writer app window.
The document salvaged later contained two partially overlaid garbled copies of the older customised diagram and no arrow!
In case it is relevant, I had three monitors attached and two of them were in HDR 4k mode. This arrangement on Windows 11 causes issues with some other software (including Microsoft Visual Studio 2022, which was also running).
Comment 1 Stéphane Guillou (stragu) 2024-02-22 15:59:50 UTC
Thank you for the report!
This sounds like the same issue as bug 132810, and the same crash signature is found there. Marking as a duplicate.

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