(gdb) thread apply all where Thread 1 (Thread 0x7f9bac9a9800 (LWP 278437) "camel-lock-help"): #0 main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/evolution-data-server-3.51.2-1.fc40.x86_64/src/camel/camel-lock-helper.c:394 (gdb) Line 394 is the while statement in this C code. d (fprintf (stderr, "parent exited, clsoing down remaining id's\n")); while (lock_info_list) unlock_id (lock_info_list->id); Reproducible: Always Steps to Reproduce: I wish I had better steps: 1. Start evolution and leave it running 2. Walk away 3. Come back some time later Actual Results: camel-load-helper process is using 100% cpu. Expected Results: camel-load-helper process should exit $ rpm -qf /usr/libexec/camel-lock-helper-1.2 evolution-data-server-3.51.2-1.fc40.x86_64 (gdb) i r rax 0x1 1 rbx 0x0 0 rcx 0x7f9bacca3cd1 140306595593425 rdx 0x10 16 rsi 0x7ffd20ff8010 140725157068816 rdi 0x0 0 rbp 0x7ffd20ff8170 0x7ffd20ff8170 rsp 0x7ffd20ff7fe0 0x7ffd20ff7fe0 r8 0x7ffd20ff7f80 140725157068672 r9 0x0 0 r10 0x0 0 r11 0x246 582 r12 0x7ffd20ff8010 140725157068816 r13 0x10 16 r14 0x7ffd20ff8020 140725157068832 r15 0x0 0 rip 0x564f6c1e85e0 0x564f6c1e85e0 <main+432> eflags 0x246 [ PF ZF IF ] cs 0x33 51 ss 0x2b 43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 fs_base 0x7f9bac9a9800 140306592471040 gs_base 0x0 0
Thanks for a bug report. I recalled I noticed this possibility upstream at [1]. I forgot of it afterwards, unfortunately. I opened [2] to track it upstream. Please see it for any further updates [1] https://gitlab.gnome.org/GNOME/evolution-data-server/-/merge_requests/149#note_1966246 [2] https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/528