Investigate and fix the memory problem in the EventBased risk calculator

Bug #1175941 reported by Michele Simionato
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenQuake Engine
Fix Released
Critical
Michele Simionato

Bug Description

We discovered in the context of a computation by Miriam (see attached files) that Python is allocating a lot of memory which is never released. The memory occupation is much bigger than the expected size of the gmvs_ruptures array. Sounds like a memory leak.

Revision history for this message
Michele Simionato (michele-simionato) wrote :
Changed in oq-engine:
importance: Undecided → Critical
status: New → Confirmed
status: Confirmed → In Progress
milestone: none → 1.0.0
assignee: nobody → Michele Simionato (michele-simionato)
Revision history for this message
Michele Simionato (michele-simionato) wrote :

Here are the pull requests: https://github.com/gem/oq-engine/pull/1167 (improved the memory profiling) and https://github.com/gem/oq-engine/pull/1166 (cleaned up the hazard getters to save memory).

Changed in oq-engine:
status: In Progress → Fix Committed
Changed in oq-engine:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.