• State Not Answered
  • Replies 3 replies
  • Subscribers 389 subscribers
  • Views 1320 views
  • Users 0 members are here
Options
Related

Memories leak when creating SDL projects automatically.

vahan Adjemian

For our business we are creating a lot of SDL projects automatically using a service which is using SDL API. The project that we created as a file which had been converted to sdlxliff and on which we performed pre-translation with memories that we have created using TMX.

Our problem is that the SDL version after SDL 2014 had introduced more memories leak which don’t allow us to upgrade to a new version because the service that is creating project is crashing. That is preventing us to use the functionality of SDL 2015.

What we identify is by just creating a project with a project template that has a size of 532Kb we are losing 4.5MG per project.

Is it possible to correct or find a bypass to this bug?
Rate translation
×
Suggest better translation
×
Parents Reply
  • 0 in reply to Romulus Crisan (former member)
    In the previous version of SDL (SDL 2014 without service pack) we were able to create automatically SDL projects. But in later version of SDL our server was crashing because more and memory ram was taken until the server crash.

    We had performed several tests and we also test to create empty SDL project with the API and loading a template with a size 532KB. What we notice is that is the size of the project template that is important not what is inside.

    By watching the memory ram on our server we can clearly see a slop and that each time we create a SDL package we are taking ram from the server that is not getting release. After a point when the server has lost too much memory SDL is crashing but we don’t have the error OutoMemoryException.
Children
No Data