Bug 1461878

Summary: crash in gst_plugin_loader_try_helper (@ gstpluginloader.c:431 of gst-plugin-scanner)
Product: Red Hat Enterprise Linux 7 Reporter: Matěj Cepl <mcepl>
Component: gstreamer1Assignee: Wim Taymans <wtaymans>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: wtaymans
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-15 07:38:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
backtrace (abrt fails to do anything for me) none

Description Matěj Cepl 2017-06-15 14:00:26 UTC
Created attachment 1288081 [details]
backtrace (abrt fails to do anything for me)

Description of problem:
When I start new gnome-session I quite often get few core dumps in my $HOME. They are all (according to file core.*) from /usr/libexec/tracker-extract, but when looking at the backtrace, it seems the crash itself is in gst-plugin-scanner run from inside tracker-extract.

I have no idea what's is the cause of this by wtay suggested that switch to using g_spawn_async_with_pipes may be the culprit.

Version-Release number of selected component (if applicable):
gstreamer1-1.10.4-2.el7.x86_64
tracker-1.10.5-4.el7.x86_64

How reproducible:
there is usually a streak (three to five or something like that) of coredumps after  start of new gnome-session (evidently as tracker rechecks content of the followed directories), then it ceases to happen until tracker is rerun.

Comment 3 RHEL Program Management 2021-01-15 07:38:16 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.