Tracker Software Products

zarkogajic wrote: ↑
Mon Feb 08, 2021 9:12 am
It actually had nothing to do with memory management, correct?

Correct.
It was because one of the Editor components entered an unexpected and unrecoverable state and reported a catastrophic failure.

zarkogajic wrote: ↑
Fri Feb 05, 2021 9:23 am
You could have take at least a few days to fix - like it took me a week to get to the bottom of it

Actually it is for your efforts that we managed to fix this quickly. Thanks and respect Žarko!

Hello researchguy007, The IDP.Generic label typically means that Avast has taken its decision based on a heuristic estimation rather than a specific malware pattern matching. Basically it means "the application can use system API in a way that resembles repertoire of identity theft malware". PDF-XCh...

Hi Žarko,
Thanks for the repro app. The issue has been fixed. The fix will be available in the upcoming build 352 of the Editor.

Hello bynkook,

When you see the issue next time please make a memory dump of the Editor process. Please look here on how to do this.
Then zip the resulting .dmp file and upload it to the Tracker Software File service.

Hi Andreas, You can make the Editor more frugal of the memory (possibly at the expense of performance) by setting "Performance.MemUsage" = <amount (in percents) of the available system physical memory> or "Performance.UseMemExact" = true "Performance.MemExact" = <number of megabytes> If your applica...

Hi AnMuWK,

Unfortunately no, you cannot use PDFXChange Editor as an out-of-process COM server.
This is because most of the Editor SDK COM interfaces are not marshallable (for performance reasons).

we are running out of memory meanwhile

Is your application 32-bit?

Hello,
For compatibility reasons and because there is no changes in SDK interfaces between V7 and V8 we decided to keep the type library version the same.

Hello ndtdanh,

this issue come back again. so boring

Please see my post above with the instructions.

Hello ndtdanh,

When you see the issue next time please make a memory dump of the Editor process. Please look here on how to do this.
Then zip the resulting .dmp file and upload it to the Tracker Software File service.

Hi René,

Please unpack the attached ZIP into an empty directory.
When you see this freeze next time please run dump.cmd as Administrator. As a result of its execution you should get Dumps subdirectory. Please send us the content of this directory (zipped).

Hello Greg, We will take a look if it is possible to further advance the IDispatch simulator capabilities to cover more SDK interfaces and IAFS_Filesys in particular. But as we stated from the beginning this simulator is a sort of trade-off to enable late binding client to access at least some of th...

Hello Greg,
The issue has been resolved in the upcoming build of the Editor.

The error you get means that COM runtime cannot start pdfSaver as a COM server. One possible reason is a delay in the server startup process. During regular printing pdfSaver is not started by COM runtime but by the driver itself and therefore is not a subject for the COM timeout. This is why I aske...

Hello Jochen,
Please try "Paper.Size" (for standard papers) or "Paper.CWidth"/"Paper.CHeight" (for custom paper sizes).

Hello, In order to collect more information on this issue please: 1. Download this ZIP file and unpack it to an empty directory. 2. Reproduce the explorer hang. 3. Run (double-click) dump.cmd . Wait until the console window closes. You should have got Dumps subdirectory at this stage. Please send it...

Hi hafeesh, If you get Blue screen (BSOD), there is no guarantee that the data the application has written to a file will be actually stored to the disk. Because Windows could be unable to flush system file cache buffers to disk. This is probably the reason why you do not get auto-recovery file afte...

doesn't setting those values essentially make the 64-bit process operate much like a 32-bit process in the way of potential memory consumption (or lack thereof)? Yes, this will prevent your application from using memory addresses over 2 GB. was that the suggested resolution to the issue or does tha...

Hello Greg C, Can you provide a minimal sample application that reproduces this issue (along with the EMF file)? Also can you please run the following command from Visual Studio Command Prompt: editbin /LARGEADDRESSAWARE:NO /HIGHENTROPYVA:NO <your application exe file> This command will modify the e...

Thank you Alex.
We have started investigation on this issue.

Does portable PDF-XChange Editor work with your datasource?

Hello Alexander,
A few questions please:
What is the process name this interaction runs in? Is it PDFXEdit.exe or PDFXHost*.exe?
Do you run 64-bit or 32-bit PDF-X Editor?
Do you provide your data source module of the same bitness as the PDF-X Editor is?

The Editor starts OK under Wine in Wayland session using Wayland reference compositor (Weston) instead of Gnome default compositor (Mutter). However the Editor UI still works unreliably (windows resizing, mouse pointer position sometimes is unrelated to the point actually clicked, etc.). So most lik...

Hi ArchStanton,

Please try to select XOrg for your login session (instead of Wayland, which is default in Fedora 30):

Thanks, now I understand.
As of the new directories - they are for our new enhanced OCR (optical character recognition) engine. Thanks for your interest.

May I know why do you need to pack the Editor DLL? Please notice that packing has some drawbacks - increased memory consumption as module memory pages cannot be shared with other processes running this module, increased memory consumption as the module pages are not backed by the module file, increa...

Hi Puffolino,
What is your Windows version?
Can you please send me your packed DLL? You can use Tracker Software File Service to upload the file. Just let me know the path you have uploaded it to.

Hello Puffolino,
What UPX options do you use to pack?
What kind of issue do you have with the packed DLL?

Hello, 1. How much time (approximately) does it take to get this exception since you execute your code? 2. Please try to execute (assuming you installed the Driver API SDK to the default directory): "%ProgramFiles%\Tracker Software\PDF-XChange 7 API\pdfSaver.exe" /show This should open pdfSaver conf...

The build will be available on our official website, as usual. No, you do not have to change anything, this feature should work transparently. However the correct work is not guaranteed for all SDK interfaces. Some interfaces are too low level to make them available for late-binding (IDispatch-based...

Hello Greg,

We have included this "feature" (or better - workaround) in the upcoming build 330 of the Editor. It will be available in the next few days.

Hi Timothy,
Please see here.

Hello Greg, As a preliminary estimation, this feature should be finished by the end of January. But it will require extensive testing to make sure our SDK interfaces remain backward compatible and do not break existing client software, as the feature will affect a lot of the interfaces. Most probabl...

Hello Greg, So when you say you "have recreated the issue", which issue exactly have you been able to recreate? We meant the NULL pointer issue. Based on our tests this occurs because PowerBuilder COM wrapping runtime does not support IUnknown based interfaces, only IDispatch based interfaces are su...

Hello Joerg,

We have reproduced the issue. I will investigate it and come back with some resolution soon.

Hi Timur,
Thanks for your detailed report. Please see your E-mail for further steps.

Hello Timur, Unfortunately I ran into the next culprit today. Trying to scan double sided pages at 200 DPI via TWAIN it turns out that once I try more than 5 pages (=10 sides) XChange does not import the pages from TWAIN anymore. 1. Assuming that: - you are still using 64-bit PDF-X Editor of build 3...

Hello mmasood, The problem occurs because you try to call PDF-XChange SDK interface method (IPXC_Inst::GetExtension) from a COM apartment that is different from the one PXC_Inst in created in. Cross-apartment call requires marshalling and PDF-XChange SDK interfaces are generally not marshallable. Sp...

Hello, We use TLB (COM Type Library) format as a universal description of our SDK interfaces. Most programming environments can translate TLB into their own native representation but the complete translation is not possible for all languages due to limitations of some languages. In your case .NET TL...

Hello sooprcow,
Can we arrange a remote debug session on one of your machines that has this issue?
See here for details.

Hi sooprcow,
We will try to reproduce the issue and figure out further steps on this.

Hello Blackhole,
Please install the latest release of PDF-XChange Editor (build 324.3).

Hello Blackhole, Thanks for the dump. We need mode detailed information about the Editor faulted state. Please unpack the attached pxe_dump.zip into an empty folder. You will get 2 files: procdump.exe (an utility to make advanced memory dumps, it is certified and signed by Microsoft) pxe_dump.cmd - ...

Hello Blackhole, Please send us a memory dump of the Editor process when you experience this issue next time. To do this open Windows Task Manager (press Ctrl+Shift+Esc ), locate PDFXEdit.exe process ( Processes tab), right-click the process and select " Create Dump File ". Then send us the resultin...

Sorry, Jeff, you have to wait until build 325. This update was not included in the final 324.3 build.
Build 325 is preliminary scheduled for April.
I have just tested the latest build snapshot of the Lite driver - /SetOptions "Save.RunApp=false" works ok.

Chris, could we arrange a remote debug session?
See here for details.

Hi Chris,
Can you check if the 32-bit Editor has this problem?
No need to reinstall, just download the portable version here - it is 32-bit.

Hello claude vidal,
Does scanning from applications other than PDF-X Editor or the Canon's utility work for you?

Hello claude vidal, We currently supply a more recent version of TWAIN DSM DLL (v. 2.3). It was supposed to resolve some issues with scanning while maintaining backward compatibility with previous TWAIN versions. But we have got several user reports that some old scanners work incorrectly with this ...

Hello claude vidal,
Just to clarify - did you ever experience that scanning freeze before you removed twain*.dll from the Editor installation directory?

Hello claude vidal,
Do you have this problem with 32-bit or 64-bit Editor?

claude vidal wrote:So what's the best option?

Please try to remove twain32.dll and twain64.dll from the Editor installation directory.
If this does not help please let us know - we might need to arrange a remote debug session.

Search found 281 matches