Message-sharing script phase 3 memory usage

Bug #464255 reported by Jeroen T. Vermeulen on 2009-10-30
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Jeroen T. Vermeulen

Bug Description

After the fix for bug 400544, only phase 3 of the message-sharing script still shows rising memory usage across transactions.

This is a simple multi-level nested loop, with all the work happening in the inner loop and plenty of reasonably safe transaction boundaries. Shouldn't be carrying many references across iterations.

Related branches

Jeroen T. Vermeulen (jtv) wrote :

Landed a fix in devel 9815 that unfortunately doesn't fix the whole problem. It does allow us to interrupt and restart the conversion of a template and still make progress.

Changed in rosetta:
status: In Progress → Fix Committed
tags: added: qa-needstesting
tags: added: qa-ok
removed: qa-needstesting

Not really qa-ok for the entire bug, but solution was eventually found and is filed as a new bug. :)

Changed in rosetta:
status: Fix Committed → Fix Released
Ursula Junque (ursinha) wrote :
tags: added: qa-needstesting
Ursula Junque (ursinha) on 2009-11-16
tags: removed: qa-needstesting
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers