Font files remain open

Aspose.PDF Product Family
1

We are using Aspose.Total for Java and we are experiencing following problem:

When we convert a document from the pdf to docx, font files (true type fonts) remain open. For instance, if we convert an attached document that uses many fonts, 15 files remain open, even after the file is closed. This doesn’t sound like much, but in our production environment, we can easily reach any limit of open files that we set to our servers, and usually, over 95% of the opened files are times.ttf.

Is there a way to make aspose close font files that it uses?

Regards,
Sofija

P.S. I am attaching our testing source code, file example and images that show that we have 15 files open after running this sample app (at the moment when the image is taken, the file is already converted, but fonts are not closed).

file1.pdf (1.3 MB)
Main.zip (682 Bytes)
15fonts.PNG (5.3 KB)
15fontsList.PNG (12.3 KB)

2

@callidus,

Kindly let us know which Aspose.Pdf for Java API version you are using. Your response is awaited.

3

We are using version 17.8

4

@callidus,

We have logged an investigation under the ticket ID PDFJAVA-37396 in our bug tracking system. Aspose.Pdf for Java API shows errors on loading source PDF file importing from the input stream. We have linked your post to this ticket and will keep you informed regarding any available updates.

However, we need to be more specific with your scenario. Kindly share all environmental details, including operating system (name and version), JDK version and IDE.

5

Hi, here is additional information:

OS Name: Linux
OS Version: 2.6.32-696.6.3.el6.x86_64
OS Distribution: CentOS release 6.9 (Final)
Architecture: amd64

JVM Version: 1.8.0_112-b15
JVM Vendor: Oracle Corporation

IDE: We are using IntelliJ Idea, version 2017.2.6 but this issue is happening on our Tomcat server.

6

@callidus,

Thank you for the details. We have logged this information under the same ticket ID PDFJAVA-37396. We will investigate in the Linux Centos environment, and then let you know about our findings. Did you try the latest version 17.12 of Aspose.Pdf for Java API? If not, then we recommend you please download and try the latest version 17.12 of Aspose.Pdf for Java API and let us know how that goes into your environment.

7

Thanks for the suggestion.
We tried 17.12 and had the same results as with 17.8

8

I apologize, I made a mistake in the original post. We are not using version 17.8 but version 17.11. Anyhow, it doesn’t work with that or the latest version.

9

@callidus,

Thank you for the details. We will let you know once a significant progress has been made in this regard.

10

Hi, is there any progress on this issue?

11

@callidus,

The linked ticket ID PDFJAVA-37396 is pending for the analysis and not resolved yet. Our product team will investigate as per their development schedules. We will let you know once a significant progress has been made in this regard.

12

@callidus,

The linked ticket ID PDFJAVA-37396 has been resolved. Please download and try the latest version 18.4 of Aspose.PDF for .NET API, and then let us know how that goes into your environment.