165135 – FILESAVE PPTX Assertion failure when saving attached PPT as PPTX

Bug 165135 - FILESAVE PPTX Assertion failure when saving attached PPT as PPTX

Summary: FILESAVE PPTX Assertion failure when saving attached PPT as PPTX

Status:	NEW

Alias:	None

Product:	LibreOffice
Classification:	Unclassified
Component:	filters and storage (show other bugs)
Version: (earliest affected)	25.8.0.0 alpha0+
Hardware:	All All

Importance:	medium normal
Assignee:	Not Assigned

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	Crash-Assert PPTX
	Show dependency tree / graph

Reported:	2025-02-08 18:25 UTC by Aron Budea
Modified:	2025-02-08 18:26 UTC (History)
CC List:	0 users

See Also:
Crash report or crash signature:

Attachments
PPT sample (227.00 KB, application/vnd.ms-powerpoint) 2025-02-08 18:25 UTC, Aron Budea	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Aron Budea 2025-02-08 18:25:47 UTC

Created attachment 199080 [details]
PPT sample

This is an assertion failure, and only occurs in builds where those are enabled, typically debug builds.

Open attached PPT in LO, and save it as PPTX.

-> You get:
Assertion failed: iter != maPlaceholderShapeToIndexMap.end(), file D:/sources/libreoffice/sd/source/filter/eppt/pptx-epptooxml.cxx, line 2484

Observed using a debug build of 25.8.0.0.alpha0+ (6042e60d69c40d1f307710e60a278cb286d68603) / Windows.

The assert is in the following line:
https://opengrok.libreoffice.org/xref/core/sd/source/filter/eppt/pptx-epptooxml.cxx?r=76c6d180f398a7d482665c24c07ec75f8a1dc7cd#2484

And was added in the following commit on 2023-12-04:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=cdb180e767ebf2011414f4a5ba7213752474ee36

I don't know if it's related, but in a daily build (non-debug), when saving the PPTX to PPT, the result is occasionally corrupted, PowerPoint can't open it. Interestingly, I've only encountered that with manual open/save, if I do --convert-to, the result could always be opened in PowerPoint. It might be worth checking separately, but only after this assertion failure is gone.