Description of problem: After upgrade evolution-calendar-factory eat a lot of memory 300G!!! And crashed when all memory is exhausted. Version-Release number of selected component: evolution-data-server-3.44.3-1.fc37 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/evolution-addressbook-factory.service cmdline: /usr/libexec/evolution-addressbook-factory crash_function: source_registry_object_added_no_owner executable: /usr/libexec/evolution-addressbook-factory journald_cursor: s=60feaa34b788404fb1cfd9bba8fe4618;i=10ed;b=e2c1e390ac7e45718098cd0f43346a17;m=186b8f9c;t=5e3de066bb6a0;x=ff0b2f951dbe9d76 kernel: 5.19.0-0.rc0.20220525gitfdaf9a5840ac.2.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #9 source_registry_object_added_no_owner at /usr/src/debug/evolution-data-server-3.44.3-1.fc37.x86_64/src/libedataserver/e-source-registry.c:867 #10 source_registry_object_added_cb at /usr/src/debug/evolution-data-server-3.44.3-1.fc37.x86_64/src/libedataserver/e-source-registry.c:883 #12 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3757 #15 add_interfaces at ../gio/gdbusobjectmanagerclient.c:1672 #16 on_control_proxy_g_signal at ../gio/gdbusobjectmanagerclient.c:1786 #18 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3757 #21 on_signal_received at ../gio/gdbusproxy.c:897 #22 emit_signal_instance_in_idle_cb at ../gio/gdbusconnection.c:3790 #26 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4230 #28 source_registry_object_manager_thread at /usr/src/debug/evolution-data-server-3.44.3-1.fc37.x86_64/src/libedataserver/e-source-registry.c:1163 Potential duplicate: bug 2094417
Created attachment 1897517 [details] File: backtrace
Created attachment 1897518 [details] File: core_backtrace
Created attachment 1897519 [details] File: cpuinfo
Created attachment 1897520 [details] File: dso_list
Created attachment 1897521 [details] File: environ
Created attachment 1897522 [details] File: limits
Created attachment 1897523 [details] File: maps
Created attachment 1897524 [details] File: mountinfo
Created attachment 1897525 [details] File: open_fds
Created attachment 1897526 [details] File: proc_pid_status
Similar problem has been detected: After upgrade evolution-calendar-factory eat a lot of memory 300G!!! And crashed when all memory is exhausted. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Evolution\x2dalarm\x2dnotify-2390.scope cmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify crash_function: source_registry_object_added_no_owner executable: /usr/libexec/evolution-data-server/evolution-alarm-notify journald_cursor: s=60feaa34b788404fb1cfd9bba8fe4618;i=1101;b=e2c1e390ac7e45718098cd0f43346a17;m=186e17b2;t=5e3de066e3eb7;x=26f66e306b71bc02 kernel: 5.19.0-0.rc0.20220525gitfdaf9a5840ac.2.fc37.x86_64 package: evolution-data-server-3.44.3-1.fc37 reason: evolution-alarm-notify killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: After upgrade systemd to 251.3-1.fc37 version, evolution-calendar-factory exhaust all memory and crashes. Downgrading systemd to previous version (251.2-1.fc37) did not helps avoid this issue. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/evolution-addressbook-factory.service cmdline: /usr/libexec/evolution-addressbook-factory crash_function: source_registry_object_added_no_owner executable: /usr/libexec/evolution-addressbook-factory journald_cursor: s=50b987753d7046a08b3abc1458bb7502;i=1e00e;b=47141e543e70475c8d50eccdbead072c;m=326c18da;t=5e3eb6a7495a2;x=293171ce43ff4136 kernel: 5.18.0-0.rc4.20220428git8f4dd16603ce834.36.fc37.x86_64 package: evolution-data-server-3.44.3-1.fc37 reason: evolution-addressbook-factory killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: After upgrade systemd to 251.3-1.fc37 version, evolution-calendar-factory exhaust all memory and crashes. Downgrading systemd to previous version (251.2-1.fc37) did not helps avoid this issue. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/evolution-calendar-factory.service cmdline: /usr/libexec/evolution-calendar-factory crash_function: source_registry_object_added_no_owner executable: /usr/libexec/evolution-calendar-factory journald_cursor: s=50b987753d7046a08b3abc1458bb7502;i=1e02a;b=47141e543e70475c8d50eccdbead072c;m=326f2e47;t=5e3eb6a77ab0e;x=68bbfed8262d3354 kernel: 5.18.0-0.rc4.20220428git8f4dd16603ce834.36.fc37.x86_64 package: evolution-data-server-3.44.3-1.fc37 reason: evolution-calendar-factory killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: After upgrade systemd to 251.3-1.fc37 version, evolution-calendar-factory exhaust all memory and crashes. Downgrading systemd to previous version (251.2-1.fc37) did not helps avoid this issue. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Evolution\x2dalarm\x2dnotify-2409.scope cmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify crash_function: source_registry_object_added_no_owner executable: /usr/libexec/evolution-data-server/evolution-alarm-notify journald_cursor: s=50b987753d7046a08b3abc1458bb7502;i=1e00b;b=47141e543e70475c8d50eccdbead072c;m=326bbfe1;t=5e3eb6a743ca9;x=9570dd87ad5c8312 kernel: 5.18.0-0.rc4.20220428git8f4dd16603ce834.36.fc37.x86_64 package: evolution-data-server-3.44.3-1.fc37 reason: evolution-alarm-notify killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Thanks for a bug report. I can reproduce it too and I figured it's a side-effect of this [1] glib2 change. I made a change upstream [2], which is built now and an update had been filled [3] for the rawhide. You should be able to update the evolution-data-server package soon, the version is evolution-data-server-3.44.3-2. [1] https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2576 [2] https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/a942d4b49 [3] https://bodhi.fedoraproject.org/updates/FEDORA-2022-c8b421c46c
Thanks for such a quick fix. Although I wrote that this happened after a systemd update, in fact it is related to the event in my calendar. A new day has come and the bug has ceased to repeat itself. I changed my computer clock to July 16 and the bug happened again. I confirms that with evolution-data-server-3.44.3-2.fc37 bug not happened with July 16.
Thanks for the confirmation. This happened when connecting to the calendar, when there were no TLS errors detected.