GTG

Huge usage of multi-parent tasks makes liblarch slow and raises tracebacks

Bug #1037792 reported by Izidor Matušov
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
GTG
Won't Fix
Critical
Unassigned

Bug Description

The attachement is the anonymized versions of my current task list. The loading time is much longer than before and applying a filter raises a traceback (Trying to remove node %s with no iterator) every time you apply a filter, e.g. selecting a tag or switching to WorkView.

To complete this bug:
1) Remove the traceback
2) Debug liblarch -> why it is so slow?
3) Optimize liblarch for this use case

Although this bug is critical and found in the testing period for GTG 0.3, it is a very very edge and rare use case. It should be solved for next releases.

Revision history for this message
Izidor Matušov (izidor) wrote :
Changed in gtg:
assignee: nobody → Izidor Matušov (izidor)
Izidor Matušov (izidor)
Changed in gtg:
assignee: Izidor Matušov (izidor) → nobody
Revision history for this message
Matthew Kress (mkress1) wrote :

I am getting the same problem with the daily ppa with gtg: 0.3.r1298~quantal1 and python-liblarch 2.2.0.r147_quantal1. My system is linux mint 14.

Revision history for this message
Will Taff (wrtaff) wrote :

Getting the same myself.

Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

Closing this ticket as we do not use LaunchPad anymore, see https://wiki.gnome.org/Apps/GTG to learn more about the current status of the project and to find the new location where our code and bug reports are hosted.

Changed in gtg:
status: Confirmed → Won't Fix
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.