Aspose.PDF memory leak issues while merging multiple pdf files and adding page number, logo?

file is private.

I didn’t understand? Let us know if you need anything from us?

Regrads,
Prathap

I couldn’t download temporary license. Getting this when I try to download file. Sorry, this file is private. Only visible to topic owner and staff members.

I have shared it in my google drive. Please try downloading using the below link.

https://drive.google.com/file/d/14-a3RVJ4sY_4JODm7y4O77nBT5uMC0k1/view?usp=share_link

@clydeu

Are you facing any issue while applying for temporary license over Aspose Website?

Nope. I haven’t had any issues so far.

Hi,

Any update on this issue or any TAT that you can give?

Thanks,
Prathap

@PrathapSV

The logged ticket is currently under the phase of the investigation and as soon as it is fully investigated, we will be able to share some reliable ETA with you. Please be patient and spare us some time.

We are sorry for the inconvenience.

Hi,

Any luck or update on rectifying this issue?

Also, if it helps, recently i had a weird observation regarding this memory leak issue. If you do not add page number or logo to each page then there is a good amount of memory leak gets reduced.

Below are my stats observed in our production version of application.

Memory after creating a PDF Book(Merging 1501 pdf files) WITH Logo and Page Number -
463MB.

Memory after creating a PDF Book(Merging 1501 pdf files) WITHOUT Logo and Page Number -
163MB.

Hope it might help your development team to investigate this issue.

Regards,
Prathap

@PrathapSV

Regretfully, no updates are available at the moment about ticket resolution. We have recorded the provided information along with the ticket and will surely consider it during issue analysis. We will notify you once we have some updates about ticket fix. Please spare us some time.

We are sorry for the inconvenience.

Hi,

It’s been more than 2 months since the last update, any update on this issue?
We have been stuck with this issue for more than 6 months now. It’s the only show stopper for us from going into the production.

We are very much waiting for this fix here, please let us know.

Regards,
Prathap

@PrathapSV

We are afraid that the earlier logged could not get resolved yet due to other pending issues in the queue. Please note that the ticket is quite complex in nature as it is about performance of the API. Your concerns have already been recorded and we are considering them during ticket analysis. We also request you please check our priority/paid support option in case this issue is a blocker for you and needs to be resolved on an urgent basis. We will inform you in case we have some updates about ticket resolution.

We apologize for the inconvenience.

It’s been a long time, Any update on the issue ?

Also, we have the same memory issue in Aspose.Slides and Aspose.PDF as well, if we opt for the paid support option, should we take two separate licenses or only one is enough to address both of the issues?

Regards,
Prathap

@PrathapSV

We are afraid that the ticket is still under the phase of the investigation. We will surely inform you once we its analysis is complete and we have some news about its fix ETA.

Furthermore, please create a post in our Purchase Forum in order to get information about the licensing.

Hi,

Any progress on this issue ? We have the Paid Support license now, just wanted to check the status before posting this issue on that channel.

Regards,
Prathap

@PrathapSV

We are afraid that no progress has been made yet as the ticket is performance related and complex in nature. Also, there are other issues logged prior to it that are under the investigation phase. You can surely use the Paid Support channel in order to expedite the investigation process and get an ETA quicker. We are sorry for the inconvenience.