Forcesave method fails when trying to save PDFs after editing

[Inso2008]

This issue is unique.

• I have used the search tool and did not find an issue describing my bug.

Operating System of DocumentServer

Debian 11

Version information

8.2.2

Expected Behavior

Hello,

we ran into some issues when trying to edit some PDF document (lorem_ipsum.pdf) through new "PDF Editor" component.

After calling the forcesave method (from new "PDF editor" component) we expect status code 6 (document is being edited, but the current document state is saved) from Callback handler.

Actual Behavior

we will get status code 7 (error has occurred while force saving the document) instead of 6 (document is being edited, but the current document state is saved).

In FileConverter.log we can then find these:

[2025-01-17T11:40:42.970] [ERROR] [localhost] [7b083451-d4bf-11ef-8794-00155d96fc7c] [userId] nodeJS - stdout:
[2025-01-17T11:40:42.970] [ERROR] [localhost] [7b083451-d4bf-11ef-8794-00155d96fc7c] [userId] nodeJS - stderr:
[2025-01-17T11:40:42.970] [ERROR] [localhost] [7b083451-d4bf-11ef-8794-00155d96fc7c] [userId] nodeJS - ExitCode
(code=0;signal=SIGSEGV;error:-80)

Reproduction Steps

1. open attached file for edit (lorem_ipsum.pdf)
2. do some change (any)
3. try to forcesave it

Additional information

The only thing these affected files have in common that we can think of is that they were created through a component dompdf.

And it's happening on desktop version too.

[TatianaKirillova]

@Inso2008 I'm happy to report that the issue is fixed and will be included in the next release. Don't miss updates. Have a nice day!