PDF-XChange Editor control issues

[bpatel]

Hi,

I have embedded the PDF-XChange Editor control in a Windows form.
I use the PDF-XChange Editor control on the Windows form for the following:
- load 3000 page PDF files
- manipulate bookmarks on the PDF file
- search the PDF file
- review the PDF file

This functionality just got deployed to Production environment and we started getting the following issues:
1) Entire application crashes randomly when:
- navigating the pages using the arrow buttons at the bottom of the editor control
- searching the 3000 page PDF file
- multiple selection of the thumbnail pages

2) Randomly get a "Document unavailable" error message pop-up when user is searching for a single word in the PDF document (1510 pages). The user clicked ‘OK’ on the pop-up message and it looked as though the document was no longer loaded. However, when he clicked on the search result in the Search Results pane, the page loaded.

3) Search functionality is very slow.

Thanks for all the help in resolving these issues.

Regards,
Bijalkumar D. Patel
Logistics Health, Inc.

[bpatel]

Here is the Event Log that was captured when the application crashed and closed without any warning or message:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<Events>
<Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'>
<System>
<Provider Name='Application Error'/>
<EventID Qualifiers='0'>1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime='2017-03-20T20:28:51.000000000Z'/>
<EventRecordID>71618</EventRecordID>
<Channel>Application</Channel>
<Computer>LHI-TRMPRD109.lhi.com</Computer>
<Security/>
</System>
<EventData>
<Data>LHI.MEDNet.exe</Data>
<Data>8.17.6279.13399</Data>
<Data>58c3fb10</Data>
<Data>PDFXEditCore.x86.dll</Data>
<Data>6.0.319.0</Data>
<Data>583cad33</Data>
<Data>c0000005</Data>
<Data>014bc620</Data>
<Data>e190</Data>
<Data>01d2a1b82c6e3b24</Data>
<Data>C:\Program Files (x86)\LHI.MEDnet\LHI.MEDNet.exe</Data>
<Data>C:\Program Files (x86)\LHI.MEDnet\PDFXEditCore.x86.dll</Data>
<Data>d3fe0f8d-0dab-11e7-8211-0025b531000a</Data>
<Data></Data>
<Data></Data>
</EventData>
<RenderingInfo Culture='en-US'>
<Message>Faulting application name: LHI.MEDNet.exe, version: 8.17.6279.13399, time stamp: 0x58c3fb10
Faulting module name: PDFXEditCore.x86.dll, version: 6.0.319.0, time stamp: 0x583cad33
Exception code: 0xc0000005
Fault offset: 0x014bc620
Faulting process id: 0xe190
Faulting application start time: 0x01d2a1b82c6e3b24
Faulting application path: C:\Program Files (x86)\LHI.MEDnet\LHI.MEDNet.exe
Faulting module path: C:\Program Files (x86)\LHI.MEDnet\PDFXEditCore.x86.dll
Report Id: d3fe0f8d-0dab-11e7-8211-0025b531000a
Faulting package full name:
Faulting package-relative application ID: </Message>
<Level>Error</Level>
<Task>Application Crashing Events</Task>
<Opcode>Info</Opcode>
<Channel></Channel>
<Provider></Provider>
<Keywords>
<Keyword>Classic</Keyword>
</Keywords>
</RenderingInfo>
</Event>
<Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'>
<System>
<Provider Name='.NET Runtime'/>
<EventID Qualifiers='0'>1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime='2017-03-20T20:28:51.000000000Z'/>
<EventRecordID>71617</EventRecordID>
<Channel>Application</Channel>
<Computer>LHI-TRMPRD109.lhi.com</Computer>
<Security/>
</System>
<EventData>
<Data>Application: LHI.MEDNet.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 5D6BC620
</Data>
</EventData>
<RenderingInfo Culture='en-US'>
<Message>Application: LHI.MEDNet.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 5D6BC620
</Message>
<Level>Error</Level>
<Task></Task>
<Opcode>Info</Opcode>
<Channel></Channel>
<Provider></Provider>
<Keywords>
<Keyword>Classic</Keyword>
</Keywords>
</RenderingInfo>
</Event>
</Events>

[Will - Tracker Supp]

Hi bpatel,

From what you have given us, we can't tell anything at all. There are several problems:
1) Please update to the lates SDK version.
2) Please try using the x64 version of the dll.
If this does not help then you will have to provide a sample that we can test and reproduce the problem.

Thanks,

[bpatel]

Hi Will,

We are currently using PDF-XChange Editor Core API ver. 6.0.319.0 and the latest version you have is 6.0.321.0. Are there any major updates in this newer version that will resolve my issues?
Also we cannot use the 64-bit version of the SDK since our entire application has been implemented for the 32-bit architecture.
Regarding the sample file, the issues are quite random. The PDF-XChange Editor control will work perfectly one time and not the second time for the same file.
Could there be any memory leak or any other performance issue in the control that could be causing this?

Thanks for all the help in resolving these issues.

Regards,
Bijalkumar D. Patel
Logistics Health, Inc.

[Lzcat - Tracker Supp]

Hi bpatel

Also we cannot use the 64-bit version of the SDK since our entire application has been implemented for the 32-bit architecture.

That's a pity for you. .Net platform has very poor memory management. This is not a big problem for x64 code, but huge for 32-bit one. Even if your PC has a lot of physical RAM 32-bit applications cannot use more than 2 GB of memory, and significant part of it used by DLLs, treads and their data. More components you are using - more memory is consumed by DLLs and treads. Also to open PDF document (and process search) we require some memory too. Most of it will be released after search is done, other - when you close document and search results. Unfortunately when .Net take references to some of our objects we cannot release them and they will consume memory until .Net will release them, and this is outside our control. So please double check code where you are using any of our objects and make sure that they will not "hang" until garbage collector will release them. In 64-bit process limits are much higher and this not cause much problems, but in 32-bit it is serious limitation. You may use vmmap.exe form Sysinternals suite to examine your process. You may do this at process start and after some work done and see what changed.

We are currently using PDF-XChange Editor Core API ver. 6.0.319.0 and the latest version you have is 6.0.321.0. Are there any major updates in this newer version that will resolve my issues?

If you have issues with memory limits - I'm afraid that none of our builds will solve them. But there was numerous fixes, so it is common rule - check latest build to make sure that problem still exist.
HTH.