This project has moved. For the latest updates, please go here.

Apparent Memory Leak During Alarm Initialization

Dec 6, 2012 at 9:41 AM

using openPDC 1.5 SP1 RC (81675), I can recreate a large memory leak by:

1. Install a clean version of openPDC, creating a new database (SQL Server 2012 Express).

2. Create a new concentrator device, referencing a UDP port, configure from production with  7 companies, 30-40 PMUs, several hundred measurements.

3. Create two Dynamic Calculations programatically (calculations using two system statistics). Works fine, by the way.

4. Create one Power Calculation programatically , which has never worked (see earlier Discussion).

5. Then create approximately 3 alarms programatically  on each measurements (total of  ~4000 alarms).

Prior to step  3, the system is stable, streaming is good. Once step 3 begins, memory use starts climbing very fast. Step 5 completes successfully, with memory generally around 4 Gb. Memory use continues to climb, although alarms are successfully and correctly raised, streaming is seemingly unaffected.

I usually stop/start the openPDC when memory use exceeds 9 Gb. At that time, all seems okay, alarms raised as expected, streaming unaffected and correct.

My next 'Discussion' is related to this one...

Dec 28, 2012 at 5:39 PM

Hasn't happened for a few weeks, and I've re-created the database, brought in 20 PMUs and related phasors, added alarms, etc. No unusual memory use seem... perhaps it 'went away'

Jan 9, 2013 at 2:05 PM

this problem, if it ever existed, no longer is a problem. Such alarms are being raised as expected.