New Blog Post: PDF/A and Metadata

Memory error on closing designer

edited June 2017 in General
Hi,
probably we have found a little memory error:

On closing the designer
destructor TppReportListView.Destroy is called by destructor
TppCommunicator.Destroy being called by destructor
TppDesignToolManager.Destroy;

Later destructor TppDataExplorer.Destroy is beeing called.
Unfortunately the previous method contains two calls

- ListView.OnChange := nil; (1666)
- ListView.OnChanging := nil;(1667)

where Listview already has been destroyed but is not nil.

This caused our memorguard (https://sourceforge.net/projects/fastmm/)
to create a valid exception:"FastMM has detected an error during a
GetMem operation. FastMM detected that a block has been modified after
being freed. "

Any ideas what to do?

Tia Carsten

--


Hint: We altered the sources!Hint: We altered the sources!

Comments

  • edited June 2017
    Hi Carsten,

    Thanks for reporting this. I created a patch for RB 18.01 to resolve this
    issue. Registered 18.01 customers can email support@ and request the patch

    (That code has been in place for many years, the memory error is not likely
    to cause a run-time error in most environments. But a diagnostic tool like
    FastMM will correctly report it).



    Best regards,

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

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited June 2017
    Nard Moseley (Digital Metaphors) machte diesen Vorschlag :

    Works as expected, great job, incredible fast response time !!!!!

    --


    Hint: We altered the sources!Hint: We altered the sources!
This discussion has been closed.