[build 403] Even after closing PDF-XChange Editor after scanning, the processes remain and continue to increase

[rakunavi]

Hello all,

Since build 403, the process persists even after closing PDF-XChange Editor after scanning. Each time the cycle of launching the app, scanning, and closing the app is repeated, the number of persistent processes increases, suggesting a high likelihood of a resource leak or process management issue. Note that in build 401, the process did not persist if PDF-XChange Editor was closed after scanning.

The verification video below shows the cycle of launching the app, scanning, and closing the app repeated twice for both build 401 and build 403. I tested this with three different scanners using both TWAIN and WIA protocols and obtained the same results, so I report this for reference.

• Canon DR-6030C
• plustek OpticBook 3600
• FUJIFILM DocuPrint M260 z

Note that while the version history indicates build 402 existed, it is unavailable for download from the download page. Therefore, build 401 was used as the comparison baseline.


build 401

• build401.webm

build 403

• build403.webm

Hoping that the above information will be of some help to you.
Thank you so much for your continued support.

Best regards,
rakunavi

- PDF-XChange Editor PRO Version: 10.7.5 build 403
- OS Version: Windows 11 Pro / Home 25H2 Build 26200.6901
- PC Model: GMKtec Nucbox M7 Pro with HUION Kamvas Pro 19 / Lenovo IdeaPad C340-15IWL

[Daniel - PDF-XChange]

Hello, rakunavi

Thank you for the report, I have reproduced the issue, and passed it along to the Dev team.

Also regarding build 402, yes it was a special internal release, and not one that ever went public. For now, it is intended to remain that way.

Kind regards,