With a large database, GRAMPS can "run out of available locks". See bug report below.

+

With a large database, GRAMPS can "run out of available locks".

+

For 140.000 people you should use: max_locks 300000 and max_objects 300000

+

+

The easiest way to do this is to create an empty database the add a file DB_CONFIG to the database directory before importing (see gramps -l output for the directory of a specific family tree. Contents of this DB_CONFIG file should be:

There have been multiple reports of long freezes and crashes of GRAMPS when refreshing the people or place tree view, e.g. after editing a person or changing the Name Display Format. They are related to the use of GNOME Assistive Technologies (ATK/GAIL).

GRAMPS runs out of locks

With a large database, GRAMPS can "run out of available locks".
For 140.000 people you should use: max_locks 300000 and max_objects 300000

The easiest way to do this is to create an empty database the add a file DB_CONFIG to the database directory before importing (see gramps -l output for the directory of a specific family tree. Contents of this DB_CONFIG file should be:

Gramps and AttributeError

This message is often related to your data into your FamilyTree.
See AttributeError

GRAMPS cannot import media with non-ASCII characters on filename

If Python returns a codec/UTF8 warning and this file was pasted from an external support (CD, HD, USB key), maybe filename has been corrupted ! It seems correct on screen but not on command line. Your OS was not able to properly set the encoding used on your external support.