Eclipse Community Forums: Gendoc

Help

Home

Home » Eclipse Projects » Gendoc » memory leak

Show: Today's Messages :: Show Polls :: Message Navigator

memory leak [message #1786243]

Fri, 27 April 2018 13:58

Carsten Pitz

Messages: 479
Registered: May 2015
Location: Germany

Senior Member

I actually experience a memory leak using Gendoc 0.7.0 Papyrus Edition.
Can anybody confirm this?
/pica

Report message to a moderator

Re: memory leak [message #1786246 is a reply to message #1786243]

Fri, 27 April 2018 14:43

Antonio Campesino

Messages: 56
Registered: August 2016

Member

Hi,

I know there have been issues with memory leaks due to the GMF / Papyrus offline rendering of the diagrams if the models are not open in the workbench. For some reason the model set can not be closed if the papyrus editor is not open. But that it is mpre related to papyrus than to gendoc.

In anycase, if you could attach an example with the gendoc template and papyrus model that reproduces the memory leak, I could profile it and see where the issue may be, and if it is on gendoc side, I can try to fix it.

Regards,
Antonio.

Report message to a moderator

Re: memory leak [message #1786285 is a reply to message #1786246]

Sun, 29 April 2018 17:21

Carsten Pitz

Messages: 479
Registered: May 2015
Location: Germany

Senior Member

many thanks for the answer.

My current example is a 23 page GenDoc script, that I do not like to publish ;-)
Each generation eats some 1 GByte of memory.

/pica

Report message to a moderator

Re: memory leak [message #1786365 is a reply to message #1786285]

Wed, 02 May 2018 07:22

Antonio Campesino

Messages: 56
Registered: August 2016

Member

Hi,

I will take a look, It will help me if you can state:

- Eclipse version.
- Papyrus version.
- Acceleo version.
- Model size and number of models.
- Are you using any profile?
- Which type of diagrams are included in the file

Thanks a lot,
Antonio

Report message to a moderator

Re: memory leak [message #1786370 is a reply to message #1786365]

Wed, 02 May 2018 08:43

Carsten Pitz

Messages: 479
Registered: May 2015
Location: Germany

Senior Member

Hi Antonio,

- Eclipse version.
Oxygen.3
- Papyrus version.
Oxygen.3
- Acceleo version.
3.7.2
- Model size and number of models.
ups, at the very moment 1 model splitted into exactly 90 small submodels. Combined size of *.uml files is 194123 Bytes. Alltogether 518.8KByte.
- Are you using any profile?
No, at the Moment just plain vanilla UML, no profiles used. Neither SysML, nor BPMN, nor fUML. BTW, Moka is installed. The Moka model checker is active.
- Which type of diagrams are included in the file
At the Moment only class diagrams and state Charts.

Thanks a lot,
Carsten

PS I hope to get the allowance soon, to publish it under the CC by-nc-sa license ;-)

[Updated on: Wed, 02 May 2018 08:44]

Report message to a moderator

Re: memory leak [message #1786424 is a reply to message #1786370]

Thu, 03 May 2018 08:21

Tristan Faure

Messages: 460
Registered: July 2009

Senior Member

Hello a tip (not sure it is documented somewhere) to reduce the memory footprint (if there are several gendoc tags)
declare the usage of the service : TagFileBuffer
@All what is the syntax do use services (i don't remember :() ? service="" or serviceId="" ?

[Updated on: Thu, 03 May 2018 08:22]

Report message to a moderator

Re: memory leak [message #1786434 is a reply to message #1786424]

Thu, 03 May 2018 09:14

Carsten Pitz

Messages: 479
Registered: May 2015
Location: Germany

Senior Member

Hello Tristan,

many thanks for that tip. I will try it.

But, since yesterday afternoon I get either a "String index out of range: 642" or a "String index out of range: 643" message on a former working GIT snapshot. I also rolled back my eclipse Installation. But that issue remains.

I asked my Business Manager to establish an NDA between us. That would allow me to send you my files for reference.

Now working on on a branch ;-)

Best regards,
Carsten

[Updated on: Thu, 03 May 2018 09:16]

Report message to a moderator

Re: memory leak [message #1786442 is a reply to message #1786434]

Thu, 03 May 2018 09:58

Antonio Campesino

Messages: 56
Registered: August 2016

Member

Hi Carsten,

I have run some huge models we have with Tristan generic template (https://wiki.eclipse.org/Gendoc/samples/genericTemplate) and I can see the Heap size in my case goes up to 1,5 GB and generate a 163 pages doc, but when the template execution finish, if I force the GC to run... The heap size goes back to around 130 -250MB... depending if I launch the generation with the model open in papyrus or with it closed...

Could you decribe the steps you do to launch the generetaion (directly or using the wizard? With the model open or with the model close...)? Could you see if forcing the GC to run, how much the heap usage goes down?

Also, you may try use Tristan template with your model, and see what happens?

Regards,
Antonio

Report message to a moderator

Re: memory leak [message #1786525 is a reply to message #1786424]

Sat, 05 May 2018 09:38

Carsten Pitz

Messages: 479
Registered: May 2015
Location: Germany

Senior Member

@Tristan -- That "String index out of range" issue was due to an unnamed Association (which is derived from uml::NamedElement) within a file not yet under GIT control.

/pica

Report message to a moderator

Re: memory leak [message #1786526 is a reply to message #1786442]

Sat, 05 May 2018 09:42

Carsten Pitz

Messages: 479
Registered: May 2015
Location: Germany

Senior Member

Hi Antonio,

here -- I forced it again -- multiple transformation runs in a row definitely make an out of memory error occur.

Currently that very Papyrus installation is configured to use up to 6GiByte of heap and 512MiByte of stack space.

/pica

Report message to a moderator

Re: memory leak [message #1786555 is a reply to message #1786526]

Mon, 07 May 2018 08:20

Antonio Campesino

Messages: 56
Registered: August 2016

Member

Hi,

I tested Gendoc 0.7 + Papyrus Oxygen.3 with a pretty big model and a generic template that itgenerate 175 pages with about 80 diagrams and I verified, in that case, there are no memory leaks.

I guess the issue is something specific in the template or in the models, it will help if we could have a sample that reproduce the issue... It may be due to a recursive fragment, an infinite loop until, an error that for some reason leave something that held the model opened in memory after the generation finish...

It may also help if you could provide the stack trace fo any exception it may be logged...

Regards,
Antonio

Report message to a moderator

Solved with GenDoc 0.7.2 for 2019-09 -- Re: memory leak [message #1815268 is a reply to message #1786243]

Sat, 28 September 2019 17:18

Carsten Pitz

Messages: 479
Registered: May 2015
Location: Germany

Senior Member

I experience no more memory leak after upgrading to GenDoc 0.7.2 for 2019-09 using the same template on the same model. Furthermore the time required on my i7-4500U based ultrabook dropped from almost 7 minutes to a pleasant 22 seconds :-)

Many, many thanks
Carsten

Report message to a moderator