==16968== 24 bytes in 1 blocks are definitely lost in loss record 7,209 of
22,411
==16968==    at 0x4A0515D: malloc (vg_replace_malloc.c:195)
==16968==    by 0x3A4DC45784: g_malloc (in /lib64/libglib-2.0.so.0.2512.0)
==16968==    by 0x3A4DC5A8B9: g_slice_alloc (in /lib64/libglib-2.0.so.0.2512.0)
==16968==    by 0x3A508167BD: pango_attr_list_new (pango-attributes.c:1111)
==16968==    by 0x72B393B: generate_attribute_list
(e-name-selector-entry.c:823)
==16968==    by 0x72B93D6: user_focus_out (e-name-selector-entry.c:1670)
==16968==    by 0x34FA951002: ??? (in /usr/lib64/libgtk-x11-2.0.so.0.2000.1)
==16968==    by 0x3A4E40D7BD: g_closure_invoke (in
/lib64/libgobject-2.0.so.0.2512.0)
==16968==    by 0x3A4E425D68: ??? (in /lib64/libgobject-2.0.so.0.2512.0)
==16968==    by 0x3A4E42730B: g_signal_emit_valist (in
/lib64/libgobject-2.0.so.0.2512.0)
==16968==    by 0x3A4E427D22: g_signal_emit (in
/lib64/libgobject-2.0.so.0.2512.0)
==16968==    by 0x34FAA8190E: ??? (in /usr/lib64/libgtk-x11-2.0.so.0.2000.1)

Reported against pango in bug 627612 but blamed on evolution:

--- Comment #7 from Behdad Esfahbod <behdad@gnome.org> 2010-08-24 19:09:24 UTC ---
This one looks to me like evolution leaked the attr-list it created.