Description of problem: Opened gpodder and it is set to automatically check for new episodes on startup via an extension. It found 2 episodes and started downloading right away. Entire desktop UI became very sluggish. System monitor showed high cpu and ram usage until the gpodder ultimately crashed and then everthing else returned to normal. Opening gpodder again with no new downloads found did not cause the same issues. Version-Release number of selected component: gpodder-3.10.2-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/bin/gpodder crash_function: _XRenderProcessPictureAttributes executable: /usr/bin/python3.6 journald_cursor: s=c08c330caf3e4a1b9faeed9af84f3e63;i=699ab;b=ad761cd1bb754f538bb35ec64e5d2a89;m=145eeb64f8;t=570ab02c87d90;x=60af3c25764cfad8 kernel: 4.17.3-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _XRenderProcessPictureAttributes at Picture.c:71 #1 XRenderCreatePicture at Picture.c:94 #2 _cairo_xlib_surface_ensure_picture at cairo-xlib-surface.c:1072 #3 fill_boxes at cairo-xlib-render-compositor.c:701 #4 composite_aligned_boxes at cairo-traps-compositor.c:1267 #5 clip_and_composite_boxes at cairo-traps-compositor.c:1792 #7 _cairo_traps_compositor_paint at cairo-traps-compositor.c:2063 #8 _cairo_compositor_paint at cairo-compositor.c:65 #9 _cairo_surface_paint at cairo-surface.c:2198 #10 _cairo_surface_create_scratch at cairo-surface.c:895
Created attachment 1457912 [details] File: backtrace
Created attachment 1457913 [details] File: cgroup
Created attachment 1457914 [details] File: core_backtrace
Created attachment 1457915 [details] File: cpuinfo
Created attachment 1457916 [details] File: dso_list
Created attachment 1457917 [details] File: environ
Created attachment 1457918 [details] File: exploitable
Created attachment 1457919 [details] File: limits
Created attachment 1457920 [details] File: maps
Created attachment 1457921 [details] File: mountinfo
Created attachment 1457922 [details] File: open_fds
Created attachment 1457923 [details] File: proc_pid_status
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.