Benny,
No, the logic will be to blame, not the programming language used. Normally we should cache people already scanned, but you must hit a bug there. You can reduce the number of generations to do the calculation?
Yes, in most cases it helps. Gramps won't give me a name for the relationship then, but it will still calculate the path(s) between persons.
In first run stoprecurrsemap == {}, so here we try to see if there are different ways to reach a person, we only discard and stop proceeding if a path to an ancestor is equal to one already found. This is done via

            for rel1 in pmap[person.handle][0]:
                for rel2 in pmap[person.handle][0] :
                    if len(rel1) < len(rel2) and \
                            rel1 == rel2[:len(rel1)]:

in the situation you claim it might be this is never satisfied, so we keep on searching.
So, perhaps add a print to see what relationship he is finding to see what pattern Gramps chokes on?

 
            for rel1 in pmap[person.handle][0]:
                for rel2 in pmap[person.handle][0] :
                    if len(rel1) <= len(rel2):
                        print ("different branches found already", rel1, rel2)
                    if len(rel1) < len(rel2) and \
                            rel1 == rel2[:len(rel1)]:

I think this print should show that the rel string keeps on getting more complicated, instead of stopping.
H'm, yes, sort of. I decided to cut off the royals from my main tree, and in that, I don't see Gramps loop on this anymore, although I do see a few print lines for one person. The royals are in a separate file now, and in that, I can simply trigger the loop.

I will export that database, and attach it to

http://www.gramps-project.org/bugs/view.php?id=6761

so you can see for yourself.

I said sort of here, because with this VORSTEN database, I see Gramps print lots lines with m's and f's, and one doesn't really look more complicated than the other. The rel strings are about 12 to 13 chars long, and the printing goes on and on and on, even with the default 15 generations setting.

regards,

Enno



Benny

thanks,

Enno


------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Gramps-devel mailing list
Gramps-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gramps-devel