Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

out of memory

edited September 2009 in General
Hi

Report Builder 11.05

We have a batch invoice process which can produce 100's of separate PDF/RAF
invoices and are now receiving calls from many customers with the error "out
of memory".

I have convinced one customer it is because he had only 2mb of memory on the
printer but now we are getting calls from other customers.

I notice that on 14/04 there was a similar problem reported and the advice
was to upgrade to 11.04 but we are already on 11.05.02

Any further advice?

Regards

Comments

  • edited September 2009
    Hi

    I do not know if this helps but this is an error log from one of our users



    last command which caused the error...
    00994865|Alarm.exe |ppProd.pas |TppProducer |PrintToPrinter
    |1798[147]|


    previous errors...
    |009944C0|Alarm.exe |ppProd.pas |TppProducer
    |PrintToPrinter |1651[0] |
    |009941F9|Alarm.exe |ppProd.pas |TppProducer |Print
    |1394[14] |
    |009941A0|Alarm.exe |ppProd.pas |TppProducer |Print
    |1380[0] |
    |009AF8B2|Alarm.exe |ppReport.pas |TppReport |Print
    |1055[5] |
    |0125F0F2|Alarm.exe |InvRB.pas |TwinInvRB
    |PrintAllBtnClick |2492[225]|
    first command

    Regards

    Philip L Jackson


  • edited September 2009
    Hi Philip,

    Do your users get this error primarily when exporting to PDF or Archive
    files? It is possible that the application may be leaking resources or
    memory. Have you tried running it through a memory manager like FastMM or
    AQTime?

    --
    Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited September 2009
    Hi

    This occurs when printing the invoice, the code...

    1. Creates a PDF which we store in a public location
    2. Creates an RAF file which we store in a database for legal reasons

    We have reverted a customer to a build of our application which uses 11.04
    and he currently has printed 40+ invoices as we speak without any problem.
    Previous attempts produced 16 or so before the out of memory occurred.

    Regards

    Philip L Jackson


  • edited September 2009
    Hi Philip,

    We made a few changes to the PDF device for 11.05 however nothing I see that
    should cause an "out of memory" error. We did not change the Archive device
    at all. If possible, please send an example that demonstrates this memory
    usage to support@digital-metaphors.com in .zip format and I'll try to track
    down the problem.

    --
    Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited September 2009

    Try using FastMM or AQTime to check the application for memory/resource
    leaks. We use both of those tools here.



    --
    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited September 2009
    Hi

    I think I have located the problem and the 1st test after I made the change
    went OK.

    For information, some weeks ago I added the ability to retain the printer
    properties into a stream so that when multiple reports were being printed I
    only had to display the print dialog once.

    The suggested solution was to save the device settings to a stream using the
    code below

    PrinterSetup.SaveDeviceSettingsToStream (myMemStream);

    As this code is in a loop, when printing multiple reports, the
    SaveDeviceSettingsToStream appears to have repeatedly added the device
    settings to the stream and after 16 or so prints the machine ran out of
    resources.

    By adding a condition to only save the device settings to the stream on the
    first loop I appear to have resolved the problem.

    Sorry to have wasted everyone's time.

    Regards

    Philip L Jackson



This discussion has been closed.