FrameMaker 8 Memory Issues

[Haem Eternal]

Hi,

      Working with FrameMaker 8, I've been finding that after opening and closing structured files, (either through the UI or through the FDK) the memory usage of Frame seems to noticable increase. This doesnt seem to happen with unstructured documents. Is this a known memory issue in FrameMaker? Is there any way around it?

Cheers

[Michael_Müller-Hillebrand]

Haem,

Yes, your observations are correct. The memory leak effect seems to depend a little bit on the type of structure of the documents, but it is there. I had an automated process opening XML files for full books which crashed FrameMaker 8 with every third or fourth book. The good news: FrameMaker 9 solved that problem.

- Michael

[ScottPrentice]

Yes .. in FM7.2 and FM8, after opening 300+ XML files in a single session FM will crash. Are you noticing this memory leak for structured binary files or XML sourced files? As Michael points out, the XML issue was fixed in FM9.

...scott

[Haem Eternal]

Thanks for the quick responses.

I am working primarily with FrameMaker binaries. We do use XML as well, but I havent tested this for leaking. The EDD that is imported doesnt seem to make any difference to the leak, it appears to relate to the number of structured elements in the document. This is a problem as we work with large numbers of very large structured documents.

[Art_Campbell1]

If it actually IS a problem in production, you should probably evaluate moving to FM 9, since Adobe will not fix bugs in releases that have reached the end of their release cycles.

Art

[Haem Eternal]

We are currently looking at upgrading to FrameMaker 9 in the future. From testing the trial version, the same issue seems to occur in both FrameMaker 9 as well as FrameMaker 8. I have raised this as a support issue with Adobe, but am yet to get anywhere.

[Art_Campbell1]

Is the trial version fully patched?

Help > About should read 9.0p255

[Haem Eternal]

Hi Art,

      Yes, I am running FrameMaker 8.0.4(8.0p277) and FrameMaker 9.0.4(9.0p255), so the issue still seems to exist currently. Is anyone else working with large filesets of FM files? If I open and close a document with a lot of elements I can easily see between 500Kb and 5 Mb of system memory not being freed up, so across the length of a session, with a large fileset, this is quickly becoming hundreds of Mbs.