Skip to content
Snippets Groups Projects
user avatar
#2073 Fix a real live leak
eileen authored
I used the same methods I had been playing with on the test class on a contribution
import script and found that the object that was increasing in memory in tandem with
me increasing iterations was an instance of DB_result

I tracked it down to here. In essence our main DAO functions clean up after themselves - e.g
when the DAO is destructed it cleans up the globals it has created.

However, this older ->query() function does not do that and each time is is called increases it's memory hold.

It's also worth better caching in this function...
3e8437f3
History

Welcome to CiviCRM

About

CiviCRM is a constituent relationship management system designed to meet the needs of advocacy, non-profit and non-governmental groups. It is an open source project, licensed under GNU AGPL 3, and coordinated by CiviCRM LLC. The project website is https://civicrm.org/

CiviCRM is released as a module that runs within the Drupal, Joomla, and WordPress content management systems.

Installation

The download URLs and installation instructions are available on our website: https://civicrm.org/download

Detailed installation instructions can be found in our sysadmin guide.

Documentation

Documentation can be found at https://docs.civicrm.org

Support

Answers for users, administrators & integrators: http://civicrm.stackexchange.com

Paid support available from https://civicrm.org/providers

Development and Bugs

Developers are highly encouraged to join chat.civicrm.org and post questions and ideas in the Developer Discussion room.

Installing the latest developmental code requires some special steps.

Report all issues to CiviCRM via GitLab: https://lab.civicrm.org/