5.4.5 Program Crashes When Merging PDF Files

[stondino00]

Seems the latest version crashes each time we try to merge pdf files in the program.

[torakiki]

Can you provide some detail? Like OS version and some log? Does it crash meaning the application closes or is the merge task that fails?

[stondino00]

Windows OS

The program force closes.

[Jannemannl07]

Hello, i had the same problem today, whenever i merge files and i open explorer to chose its destination it chrashes. Im on windows 11, 25h2, pdfsam version 5.4.5.
Also windows event viewer gives me this information:

Faulting application name: pdfsam.exe, version: 5.4.5.0, time stamp: 0xa6d0ca15
Faulting module name: msvcp140.dll, version: 14.31.31103.0, time stamp: 0xf632f325
Exception code: 0xc0000005
Fault offset: 0x0000000000132a8
Faulting process ID: 0x2B88
Faulting application start time: 0x1DC94EF377BF634
Faulting application path: C:\Program Files\PDFsam Basic\pdfsam.exe
Faulting module path: C:\Program Files\PDFsam Basic\runtime\bin\msvcp140.dll
Report ID: c35246ba-8164-4f9c-896e-cf056c9e6861
Faulting package full name:

Faulting package relative application ID:

Faulting module name: msvcp140.dll, version: 14.31.31103.0, time stamp: 0xf632f325
Application: pdfsam.exe
Framework version: v4.0.30319
Description: The process terminated due to an unhandled exception. Exception information: Exception code c0000005, exception address 00007FFC954B32A8
Stack:

Application: pdfsam.exe
Framework version: v4.0.30319
Description: The process terminated due to an unhandled exception.
Exception information: Exception code c0000005, exception address 00007FFD474932A8
Stack:

It is translated form dutch so i could be why its a bit different than normal.

I have already reinstalled both pdfsam and visio c++ the newest version. both of those things didnt change anything. I would love to hear a solution!

[torakiki]

There is a pdfsam.bat script in the installation directory that will start the application leaving the shell window open, could you try from there? Maybe there are more details there

[torakiki]

I just tested on Windows 11 (10.0.26200), the Merge tool specifically, and all worked correctly... not sure how to reproduce it...

[Jannemannl07]

Ok i'll try it in 2 days, tomorrow im free from work, and let you know!

[Jannemannl07]

https://github.com/user-attachments/assets/32856c5e-e433-4d85-9361-e5e572edf72f
this is what it does, if i merge to the same folder it works, but when i browse for a different location than it crashes

[Jannemannl07]

this is what event viewer says, hope it helps, im now also going to test if it also happens in previous updates

[torakiki]

Great, thanks, at least we have the steps to try to reproduce it. I'll give it a try this afternoon.

[Jannemannl07]

Do you already have a (temporary) workaround? i've also got multible clients having this problem now

[torakiki]

Maybe... we haven't been able to reproduce but I have a hunch. Could you please test the .zip bundle and see if it gives the same crash? https://github.com/torakiki/pdfsam/releases/download/v5.4.5/pdfsam-basic-5.4.5-windows-x64.zip
Also, would you be able to test a previous version to see if the issue was there already?
Thanks.
I'll try to create a test bundle this afternoon

[Jannemannl07]

For my it magically works now, i will ask my client tomorrow if it works for her. I've tested until 6 older versions and it kept happining.
Could it be that c++ redistributable update or Java update? atm it works for me. I'll let you know if it works for my client

[torakiki]

My understanding is that the issue is with the version of the msvcp140.dll file which is somewhat old in the liberica jdk (the one bundled with PDFsam). Others experiencing similar issues had success by using other jdk distributions with newer versions of it or by deleting the .dll from the runtime, forcing the jdk to use the system wide installed version.
In the linked issue they are discussing weather they should update the .dll in liberica or not but the thing is the issue is not reproducible and there must be some other moving part in place because the .dll version was the same for multiple releases and the issue came up now.... and now it started working for you so yes, maybe some system update.. not sure

[Jannemannl07]

Ok thank you, i'll try to figure it out