FlushRtfLine(B) Ran out of memory

[kepNCI]

Is it just me or is v11 throwing more out of memory errors than v9 or v10?

Quite possible it is just me as I am going through my templates and modifying them to take advantage of v11 generate documentation enhancements.

For example I have a package with one diagram. The diagram defines 71 small screens using simpleDialog. On an average each screen has 5 simple controls. The diagram also has links to 19 database tables where I have created realization relationships between the UI Control and its source database table and column via link to element function.

Using the stock Diagram Report template with no TOC, Stylesheet of Cover Page, the Generate Documentation throws the FlushRtfLine(B) Ran out of memory error while still Analyzing the model structure.  When you click OK, the progress quickly runs through the elements and then states "Document successfully created", but it has no diagram.

I am running on a PC with 16 GB RAM and system information shows 11 GB RAM still available when the error is thrown.  I am assuming this is more complicated than just a physical RAM issue.

Other diagrams will also run out of memory but cannot received causing Windows to terminate EA.

I noticed some previous posting (I think over a year ago) regarding the out of memory error where SPARX was working with the third part that wrote the Generate Document function for a solution. Is this the same problem or is this new?

[Eve]

The use of template fragments in v11 does use more memory, and it's not an issue of physical ram. (A 32 bit application can usually only address 2GB although there are ways to extend this up to 3 or 4)

I'm not sure what is causing your exact issue. You may get further by ensuring a metafile is used for diagrams.

[Stefan Bolleininger]

Hi,

within this bug, you need to look at the apearing windows.

If your bug-Windows appears your have 4-8seconds time to say OK and it resumes correctly.

If you are below four secords, it will mostly fail.
If you are above 8 seconds, it will mostly fails.

I had this issue on very, very long documents in the past, but not within the latests versions. I will check out for it.

Regards

Stefan